# API Versioning

The Monta API uses semantic versioning. Include the `Monta-Version` header in every request to specify which version you're targeting.

***

## Current Versions

* **v1**
  * Header: `Monta-Version: v1`
  * Stability: Stable
  * Notes: Default if no header is sent

* **v2**
  * Header: `Monta-Version: v2`
  * Stability: Beta
  * Notes: May change without notice

***

## Sending the Version Header

**Monta-Version**: v1

If you omit the header, requests are automatically routed to **v1**. Existing integrations will continue to work without modification.

***

## Migrating from Date-Based Versions (Deprecated)

The previous date-based version identifiers are deprecated and will be removed on **1 January 2028**.

### Mappings

* `Monta-Version: 2024-01-18` → `Monta-Version: v1`
* `Monta-Version: 2024-07-01` → `Monta-Version: v2`

***

## Deprecation Signals

If you are still using a date-based version, responses will include:

```
Deprecation: true
Sunset: Sat, 01 Jan 2028 00:00:00 GMT
X-Api-Version-Hint: Use 'Monta-Version: v1' instead of '2024-01-18'`
```

**Update your integration at your earliest convenience — before 1 January 2028.**
