Operations | Monitoring | ITSM | DevOps | Cloud

We launched the StatusGator v3 REST API back in October, and it has only gotten better since. v3 is a ground-up redesign built around organization-level API tokens, a consistent response format, opaque string IDs, pagination, and a large set of write endpoints for managing monitors, incidents, and subscribers. We have kept shipping new capabilities for it, and we will keep doing so. v2, on the other hand, is done.

No matter how fast we build, we'll never integrate with every tool. There are too many, new ones appear constantly, and some are too niche to ever reach the top of our roadmap. So if the tool you care about isn't supported yet, your options have been to wait for us to get to it, or build it yourself with our Web API plugin — a powerful, flexible option, though one that asks you to map out the endpoints, authentication and paging yourself.

Spring Boot version upgrades—whether moving from 2.x to 3.x, 3.x to 4.x, or even minor bumps like 3.2.5 to 3.3.1—regularly introduce subtle, breaking changes that unit and integration tests miss. JSON serialization shifts, autoconfiguration reordering, and transitive dependency conflicts can silently alter your API contract.

We’re excited to announce expanded functionality for the StatusGator Boards API. You can now create new boards, update existing boards, and delete boards directly through the API. Previously, the Boards API only supported listing boards and retrieving board details. With these new capabilities, you can automate the complete board lifecycle – from provisioning new boards to managing ownership and cleaning up boards that are no longer needed.

The rise of AI-assisted coding has transformed how software is built. With tools generating entire features in seconds, the bottleneck is no longer writing code—it’s verifying it. Because AI can generate boilerplate and handle API integrations instantly, more service changes are being pushed into authentication logic, API calls, and configurations. Teams desperately need a way to verify these changes before merging, especially when the code touches external dependencies.

You get an infrastructure alert. Something's off, so you task your agent to investigate, and it ends up grepping through the logs. You both wonder if there's customer impact. There’s a simple rule: AI agents in the incident loop are only as good as the signal you feed them. And logs alone aren't a great signal.