---
title: "Versioning"
description: "Learn more about Versioning in this Ordering API guide for developers integrating the platform."
canonical: https://docs.ordering.co/api-reference/guides/versioning/
---

# Versioning

The Ordering API includes its contract version in every tenant-scoped request path:

```text
https://api.ordering.co/{version}/{lang}/{project}/{resource}
```

For example:

```text
POST https://api.ordering.co/v400/en/YOUR_PROJECT/auth
```

- `version` selects the API contract, such as `v400`.
- `lang` selects the language used by API responses; it is independent from the documentation interface language.
- `project` selects the Ordering tenant.

The route format accepts a lowercase `v` followed by digits, but the server only serves versions enabled in its runtime configuration. An unsupported version returns `404` with an empty response.

A different version can resolve to a different implementation of the same controller. Pin integrations to the version they were built and tested against, and review the target version before upgrading. The version segment does not, by itself, guarantee backward compatibility with another version.