API
Versioning
API versioning strategy, version lifecycle, and deprecation policy.
Overview
The DMTR API uses URL-based versioning. All endpoints are prefixed with the version number:
https://api.dmtr.ai/v1/positions
https://api.dmtr.ai/v1/transfers/evaluateVersioning strategy
URL-based versioning was chosen for explicitness and tooling compatibility. The version is part of the path, making it visible in logs, documentation, and client code. All routes in the current API are under /v1/.
No breaking changes are introduced within a version. New fields may be added to response objects (additive changes), but existing fields are never removed or changed in meaning within the same version.
Version lifecycle
| Phase | Description |
|---|---|
| Active | Current recommended version, fully supported |
| Deprecated | Still functional, sunset date announced, migration guide available |
| Retired | Returns 410 Gone with a pointer to the current version |
Deprecation policy
- Minimum notice: 6 months before a version is retired
- Sunset header: Deprecated versions include a
SunsetHTTP header with the retirement date - Migration guides: Published with each new major version
- No silent removal: Every deprecation is announced in the Changelog and via webhook notifications (when available)
The current API version is v1. There are no deprecated versions. Subscribe to the changelog for announcements on future version transitions.