The REST API uses dated versions. A version is a date such as 2026-07-14. You pin a
version so your integration keeps behaving the same way as the API evolves.
Send the version you built against in the Nemu-Api-Version header.
If you omit the header, the request uses the latest version. Every response echoes the
version it was served with in the same Nemu-Api-Version header.
Relying on the latest version means your app can change behavior when a new version ships.
Pin a version in production.
Discover the latest version
GET /api/version is public and needs no token. It reports the current major version, the
header name, the latest dated version, and every supported version.
Unsupported versions
If you send a version that is not in the supported list, the API rejects the request with
400 and returns the versions it accepts.
Pin the version in the SDK
The SDK sends the latest version it knows about by default. Pass api_version to pin a
specific version, and read the versions from the exported ApiVersion enum.
The SDK also exports an ENDPOINTS map that describes every endpoint, the methods it
accepts, and the version it was introduced in.
What is versioned
The major version lives in the path as /api/v1. The dated version selects behavior
within that major version. The authorization endpoints, the token endpoint, and the version
endpoint are unversioned and do not take the header.