Skip to main content

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:
When omitted, the latest version is assumed.

Discover Versions

Returns every supported version, oldest first, with latest naming the one used when you omit the header:
label is a long prose string; it is abbreviated above. sunset is present only on versions that have one — no version is currently deprecated, so the key is absent from all four entries.
Pin new integrations to 2026-07-24 — the value of latest, not the literal string. 2026-05-10 is still accepted, but it predates the entire headless agent stack; 2026-07-22 is a valid pin even though it is easy to miss between the two Tier releases. See the changelog for what each date added.

Deprecation Policy

  • 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

Response Headers