Versioning

The API supports two versioning strategies:

Major Version Path Prefix

• Endpoints are prefixed with version number: /v1/, /v2/ etc

• Major versions run in parallel to maintain backward compatibility

• Breaking changes require incrementing the major version

Monthly Release Versions

• Monthly releases use the tokensource-version header parameter

• Format: YYYY-MM (e.g. 2024-03)

• Allows for non-breaking changes and feature additions

• Clients can pin to specific monthly versions for stability

• Latest version used if no header specified

Example:

GET /v1