This is easily the biggest release I've ever shipped for Telebugs. Not just one or two new features, but an entire REST API that turns the product into something you can build on, plus a sweeping UI refresh that makes everything feel more consistent and modern. I've been heads down on this for months, and it shows.
If you've ever wanted to script your error tracking, pull data into your own dashboards, automate compliance tasks, or just stop clicking around so much in the UI, this one's for you. And that's before we even get to the future stuff the API unlocks.
The REST API
The real star of 1.16.0 is the REST API. This is the first time Telebugs has had a proper, documented API surface you can actually build against. It covers projects, groups, reports, apps, webhooks, project users, and data retention policies. Everything you interact with in the UI is now available over HTTP with the same API key you use for other things.
The groups list endpoint got the most love because that's what most people hit first when they want to build a dashboard or a custom view. It supports a real query syntax right in the ?query= parameter. Filter by severity, use negation, combine things with OR. Groups themselves also finally report a proper severity value (the highest one we've ever seen for reports in that group).
Example request to the Telebugs REST API.
Data retention is fully programmable too. You can read and update the policies for both error data and artifacts through the API. Set retention periods, turn time-based or disk-based purging on or off, control what happens to old releases. It's the same stuff you configure in the UI, now available for scripts and external systems.
There are also endpoints for managing users on projects, working with webhooks and their deliveries, and pulling reports. The whole thing uses the same authentication model as before.
This is just the surface. Full details, all the endpoints, request/response examples, and authentication notes live in the REST API documentation. Go there for the real reference. This post is just to get you excited about what's now possible.
Error Handling That Actually Makes Sense
One thing that always annoyed me about building against APIs is when errors are just a vague status code or some ad-hoc JSON. As part of shipping the real REST API I standardized everything on RFC 9457 Problem Details.
Now when something goes wrong you get back a proper application/problem+json response. 401s for bad auth, 403s when you don't have permission (like trying to touch data retention as a non-admin), 422s with a nice errors object when validation fails. Each one has a stable type URL, a title, the status, and a human-readable detail. It's the kind of thing that makes writing a client actually pleasant instead of a guessing game.
UI Refresh and Design Consistency
While I was deep in the API work I also took the opportunity to clean up a bunch of the day-to-day UI. It had been nagging at me for a while.
The biggest visible win is consistency. Rounded borders are now the same everywhere, spacing feels more deliberate, and the whole interface has a more cohesive look. Small things like button states and divider margins got attention too.
Rounded corners are consistent across buttons, cards, and pills.
I completely reworked the project access and notification preference pages. They now have proper breadcrumbs, nicer headers with icons, a cleaner list-style display for users, flex layouts that actually make sense, and an admin role switcher that doesn't feel tacked on.
Almost every toggle in the product went from a plain checkbox to a proper switcher component. Notifications, access controls, and webhooks feel nicer to use now.
Redesigned project access page.
I also shipped a proper tooltip system. I replaced the old native JavaScript confirm dialogs with a custom confirm dialog controller so destructive actions and important settings give you better feedback instead of just doing the thing.
Custom confirm dialog replacing the old native JavaScript dialogs.
Oh, and I changed how toast notifications work. They now appear from the top for better consistency with everything else in the interface.
Toast notifications slide down from the top.
None of these are revolutionary on their own, but together they make the whole app feel more polished and intentional. The dashboard is just nicer to live in every day.
What's Next
The REST API isn't just about the features that shipped in 1.16.0. Having a real programmable surface changes what becomes possible. One of the things I'm most looking forward to is building an MCP server on top of it. That will let other tools and future AI agents talk to Telebugs in much richer ways than a simple webhook ever could. Things like querying your error data, triggering actions, or integrating deeply with your existing workflows.
It's early days, but the foundation is now there. More on the MCP server as it comes together.
Other Improvements
There were plenty of smaller things that added up. User management endpoints made it into the REST API so you can script who has access to which projects without touching the UI. Reports responses got richer with more attributes and associations. There's now a little badge on the grouping button that shows how many groups have been merged into one. I cleaned up some JSON response shapes and pagination logic across the API, added proper validation for things like non-existing project IDs when creating apps, and shipped the usual collection of bug fixes and dependency bumps.
Full list in the changelog.
Wrapping Up
This really is the biggest release I've done for Telebugs by a decent margin. The REST API turns it into something you can properly integrate with and build on top of instead of just a UI you click around in. The product itself got a serious polish pass with consistent design language, redesigned management pages, better notification behavior, a new tooltip system, and all the little details that make daily use feel better.
It's live right now. Pull the latest and give the REST API a spin. If something in the API feels off or the new UI bits aren't quite clicking for you, just drop me a line at [email protected]. I am also on X at @kyrylo and @TelebugsHQ.