Versioning & changes
One version, additive changes, and what counts as breaking.
/api/v1 is the only version. There is no date header, no version parameter and no per-client pinning — the surface is small enough that a second scheme would cost more than it protects.
Additive, and what that allows us
New fields appear in responses without notice, and new events appear in the webhook list without notice. Both are safe if you ignore what you do not recognise: parse permissively, switch on the event names you handle, and let the rest fall through. An integration that throws on an unknown field has made an additive change into an outage.
What we treat as breaking
Removing or renaming a field, narrowing an accepted value, changing what a status code means, or changing the signature scheme. Those would ship as /api/v2 with both live during a migration window — they have not happened, and v1 is the only version that has ever existed.
Deprecations
Announced on this page and in the product console before anything stops answering. Credentials are the exception in the other direction: a key you revoke stops working immediately, on purpose.