Versioning & retention

Versioning

The current version of the API is v1. It appears in every URL (/v1/…) and in every webhook event ("api_version": "v1").

Within a version, changes are additive only:

• new endpoints, new optional parameters, new event types;
• new fields in responses and payloads;
• new values in enumerations (a new alert kind, for instance).

A field is never removed or renamed within a version, and its meaning never changes. Write your integration to ignore fields it does not know, and to handle unknown enumeration values gracefully.

Breaking changes would ship as a new version (/v2), announced in the changelog long in advance, with both versions running side by side.

Retention

Older records are purged automatically every day. Revoked API keys are kept, so the history of who had access stays auditable.