Versioning

The API is versioned in the URL path; the current version is v1 (e.g. /v1/speech-to-text/prerecorded).

Backwards Compatibility

Within a version, changes are backwards compatible. We may add new response properties and new optional parameters, but we do not remove or repurpose existing ones unless we have verified that a feature is unused. Write clients that ignore unknown fields, so additive changes never break them.

Staying Up to Date

Improvements to the transcription pipeline are rolled out server-side. Requests always run on the current pipeline - there is nothing to upgrade or migrate on your side.

A new major version (e.g. v2) would only be introduced for changes that cannot be made compatibly. When that happens we will announce it, and the previous version will keep being supported - existing integrations continue to work without changes. Until then, there is no versioning to be concerned with.