API versioning overview
Marmin API versioning is header based and controlled per request.
Use the request header X-MARMIN-VERSION to select which API contract should be applied.
Available versions
20260101(default)20260507(latest)
How version selection works
If
X-MARMIN-VERSIONis not sent, the API uses20260101.If
X-MARMIN-VERSION: 20260507is sent, the API uses the latest contract.Version selection is request scoped, so keep the same header value across related API calls in one workflow.
Header examples
Default behavior (header omitted):
POST /api/sales-invoices/{business_profile_id}
Authorization: Bearer <access_token>
Content-Type: application/jsonLatest version behavior:
POST /api/sales-invoices/{business_profile_id}
Authorization: Bearer <access_token>
Content-Type: application/json
X-MARMIN-VERSION: 20260507