Versioning
Date-stamped API versions, pinned per request or per key.
The API surface is versioned with date stamps. Pin one per request with the
optional SpreadSpace-Version header:
Resolution order
Each request resolves its version in this order:
- The
SpreadSpace-Versionheader, if sent. An invalid value returns400 invalid_version. - The API key’s pinned version, if one is set.
- The latest supported version.
Supported versions
2026-07-19(latest)2026-05-03
Detecting drift
Every response echoes the resolved version in the SpreadSpace-Version
response header, so a client can detect drift between what it sent and what
the server resolved.
Future breaking changes ship under new date stamps; existing callers keep the version they pinned.