HTTP headers
The API supports a variety of HTTP headers.
The API supports the following HTTP headers.
Supported HTTP headers
Key
- {header name} (Request/Response)
- {comment}
Headers
Accept
(Request)- By default, do not pass this header; text/csv can be passed only in supported API operations
Authorization
(Request)- Authentication and authorization data
api-version
(Request)- Major.minor: 1.0
kronos-tid
(Response)- UUID for tracking requests
Content-Type
(Request)- application/json or text/csv (for supported API operations)
Content-Location
(Response)- URI representing the current status of an asynchronous request
next-ping
(Response)- Retry in seconds for an asynchronous request
Retry-After
(Response)- Retry in seconds after status 429 or 503; if not present with 503, do not automatically retry
WWW-Authenticate
(Response)- For 401 (Unauthorized) responses
X-Currency
(Request/Response)- Standard currency codes
Standard HTTP headers
Almost every API call requires the following standard headers:
content-type : application/json
Authorization : <<access_token>>
Note: Replace<<access_token>>
with the token generated during the Generate a token exercise.
Updated 8 months ago