Versioning & stability
What we may change without warning, and what we may not.
The version is in the path: /api/v1/. While v1 is live we
will not remove an endpoint, remove a field, rename a field, or change the type or
meaning of an existing field.
What may change without notice
- New fields may appear in any response. Parse defensively and ignore what you do not recognise — do not fail on unexpected keys.
- New endpoints may be added.
- Interpretation wording may be improved. The structure stays.
- Credit costs may be adjusted with notice to active accounts.
Breaking changes
Anything breaking ships as /api/v2/. When that happens,
v1 keeps running for at least twelve months and we contact every active
account before the deadline. You will not wake up to a broken integration.
Building to last
Treat unknown fields as additive, do not depend on key ordering in JSON objects, and store our identifiers as opaque strings rather than parsing them.
Last updated 13 August 2026.