> For the complete documentation index, see [llms.txt](https://docs.api.ecoinvent.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.api.ecoinvent.org/getting-started/api-versioning.md).

# API Versioning

**The ecoinvent API uses URL-based versioning.** Both the ecoinvent data version and the API version are embedded in the endpoint path, making every request fully explicit and unambiguous.

### **URL structure**

All endpoint URLs follow this structure:

```
https://api.ecoinvent.org/{data-version}/{api-version}/...
```

For example:

```
https://api.ecoinvent.org/v3/api1/datasets/search
```

These two segments are distinct concepts:

* **Data version** (e.g. `v3`, `v4`) — the version of the ecoinvent database you are querying.
* **API version** (e.g. `api1`, `api2`) — controls the behavior, response structure, and available features of the API itself.

### **Versioning policy**

We aim to maintain stability within a major API version. Breaking changes, such as modifications to response structures or endpoint behavior, will only be introduced in a new API version (e.g. `api2`). When a new version is released, the previous version will enter a deprecation period during which it remains available but is no longer actively developed. Deprecation timelines will be communicated in the [Release Notes](/release-notes/changelog-v3.md) and via direct communication to affected customers.

### **Version history**

<table><thead><tr><th width="125">API Version</th><th width="141">Base path</th><th width="146">Status</th><th>Notes</th></tr></thead><tbody><tr><td>api1</td><td><code>/v3/api1/</code></td><td>Current</td><td>Commercial release, see <a href="/release-notes/changelog-v3.md">Release Notes</a> for changes from beta</td></tr><tr><td>0 (beta)</td><td><code>/v0/</code></td><td>Deprecated</td><td>No explicit API versioning during beta</td></tr></tbody></table>