[DOCS]
Versioning
The API is versioned in the request path. Integrations built against /v1 remain stable: breaking changes are only released under a new path version.
Compatibility policy
| CHANGE | POLICY |
|---|---|
| Additive changes | New models, optional request parameters, and response fields may be introduced without notice. Clients should ignore unrecognized response fields. |
| Breaking changes | Breaking changes are not made to /v1. A breaking revision would be released as /v2, with both versions operated in parallel. |
| Error codes | Error codes are stable identifiers. New codes may be added; existing codes will not change meaning. |
| Unknown request params | Unrecognized request parameters are ignored. |
| Deprecations | Announced on this page and via email to affected accounts, with a migration window. |
Current version
v1 covers POST /v1/chat/completions and GET /v1/models.