Versioning & deprecation
Every route lives under /api/v1. Within v1 we only add — we do not break your integration.
| Kind of change | How it ships |
|---|---|
| New routes, new optional parameters, new response fields | Any time, recorded in the Changelog. Your code must ignore unknown fields. |
| New webhook events, new fields in data | Any time. Payloads are append-only — fields are never renamed or removed. |
| New MCP tools | Any time; MCP clients see them in tools/list. |
| Changing/removing a route, field or event (breaking) | Announced ≥ 90 days ahead in the Changelog and by email to the support address of every app using it; large changes ship as /api/v2 running side by side. |
Route, event and tool descriptions on this site are generated from the running code — the docs never lag behind the API.