Backwards and forwards compatibility

Trinsic designs and sunsets APIs to ensure backwards compatibility for at least 90 days. As a result you may occasionally see API responses that include fields which are no longer, or not yet. documented.

The source of truth for correct, current API usage is always our latest latest SDKs or OpenAPI specification. These reflect the actively supported API surface and should be relied on over observed response or request shapes.

We publish future changes on an ongoing cadence. As with backwards-compatible changes, new properties may appear in requests or responses before they are formally documented. One published, the API surface is considered stable and maintained.

We recommended using our published SDKs and an automatic dependency update checker to stay current with platform changes. If our SDKs do not fit your use case, use the OpenAPI specification to generate or build your own internal SDK; it serves as the authoritative guide for additions and deprecations.

In rare cases, a breaking change may occur without a change to the API surface, for example when an integration stops publishing a field to our normalized identity data model. These changes are explicitly called out in our breaking change announcements.

All breaking changes are published on our Updates page, announced via email to all active registered accounts and accompanied by new SDK releases and updated samples.