# Quest Portal public API lifecycle

Quest Portal's public REST API uses major versions in the URL, such as `/api/v1`. Breaking changes use a new `/api/vN` path. Compatible additions may be made within the current major version.

When Quest Portal deprecates a public API version, it will:

1. Announce the deprecation at least 90 days before removal.
2. Return the RFC 9745 `Deprecation` response header when deprecation is announced. Its Structured Field Date identifies when deprecation takes effect, which may be in the future.
3. Link this policy with `rel="deprecation"`.
4. Return the RFC 8594 `Sunset` response header once a retirement date is scheduled. The sunset date will not precede the deprecation date.

The current `/api/v1` pricing endpoint is not deprecated and therefore does not return `Deprecation` or `Sunset` headers today.

- [OpenAPI description](/openapi.json)
- [RFC 9727 API catalog](/.well-known/api-catalog)
- [Developer resources](/developers)