Additional Request Requirements
In addition to the security requirements, every request must include the following headers.
Request ID
All API requests must include a RequestID header containing a unique, randomly generated v4 UUID. This is used for idempotency. If you send a request with a RequestID that has already been processed, you will receive an HTTP 409 Conflict response.
Request IDs are scoped to your Organisation when performing idempotency checks. Seperate organisations can use the same RequestID without triggering a 409 response.
Plain text
Timestamp
All API requests must include a Timestamp header containing the current time in ISO 8601 format (UTC). Requests with a timestamp that is in the future or more than 5 minutes in the past will be rejected with an HTTP 401 Unauthorized response.
Plain text
Was this section helpful?
On this page
- Additional Request Requirements