API Versioning

NexSpace uses date-based API versioning via the NexSpace-Version header.

How It Works

Send the NexSpace-Version header with a date to pin your requests:

curl -H "Authorization: Bearer nex_live_YOUR_KEY" \
     -H "NexSpace-Version: 2026-05-10" \
     https://api.nexspace365.com/api/facilities

When omitted, the latest version is assumed.

curl https://api.nexspace365.com/.well-known/api-versions

Returns all supported versions:

{
  "versions": [
    {
      "date": "2026-05-10",
      "label": "Initial public API",
      "sunset": null
    }
  ],
  "latest": "2026-05-10"
}

12-month deprecation window — deprecated versions include Deprecation and Sunset headers in responses
Sunset versions return 410 Gone — migrate before the sunset date
Breaking changes only ship in new version dates
Non-breaking additions (new fields, new endpoints) are added to all active versions

Header	When	Description
`NexSpace-Version`	Always	The version used for this response
`Deprecation`	Deprecated versions	RFC 8594 deprecation date
`Sunset`	Deprecated versions	RFC 8594 removal date