Continuous API monitoring
Stripe, OpenAI, GitHub, Cloudflare and more. When a provider changes its API, you know about it.
Driftwatch monitors the third-party APIs your product depends on and alerts you to the changes that break your code.
No error is raised. The value is ignored and your results change silently, which is the hardest class of break to notice.
Code that breaks
await client.post("/v2/sandboxes/sessions/{sessionId}/cmd", {
// cmdId is now ignored, not rejected
cmdId: value,
});
APIs Driftwatch watches
Know what changed, what it breaks, and how to fix it.
Every alert shows the code that fails, so your team knows where to look.
switch (payment.status) {
case "succeeded": …
case "failed": …
// "requires_review"
// has no branch
}
The GitHub App opens a pull request with the fix, ready for your review.
Changes are judged by their effect on your code, not on the provider’s.
Every change is classified by published rules, so the same change always gets the same verdict.
Follow every API, or only the ones you use, by RSS or JSON feed.
Some changes a provider considers safe are exactly the ones that break the code calling it. Driftwatch catches them.
What their changelog says
Safe for them: every response they send is still valid.
What your code sees
Code that reads the field without a check throws on every response that leaves it out.
const { city } = customer.address;
// TypeError: Cannot destructure property 'city'
// of 'customer.address' as it is undefined.
A real Plaid change, end to end.
Plaid renames a field in its API.
ProtectEventSendRequest:
properties:
- protect_session_id:+ device_session_id: type: string
You get an alert with what breaks and the code that fails.
The GitHub App opens a pull request with the fix, ready for review.
- protect_session_id: sessionId,+ device_session_id: sessionId,
Join early access to the GitHub App, and get a pull request when an API change breaks your code.