Versioning
The 401GO API employs a header-based versioning scheme. Versioning is done per-endpoint with a provided date header.
Endpoints accept an optional Api-Version header, which is an ISO date string (YYYY-MM-DD).
- If provided, the API will use the version of the endpoint corresponding to the date specified in the header. If the date falls between two published versions, the API will use the latest version that is older than or equal to the given date.
- If omitted, the API defaults to the version that was current on the date your application was registered in our system.
We recommend always building to the latest version of the endpoint, but any existing integrations will retain backwards compatibility.
Updated 30 days ago