CB-ACCESS-KEY
: The API key as a stringCB-ACCESS-PASSPHRASE
: The Passphrase shown when creating the API keyCB-ACCESS-SIGN
: The Base64-encoded signatureCB-ACCESS-TIMESTAMP
: A timestamp for your requestCB-ACCESS-TIMESTAMP
header MUST be number of seconds since Unix Epoch in UTC. Decimal values are not allowed. Make sure to use an integer.
Your timestamp should be within 5 seconds of the API service time or your request is considered expired and will be rejected.
CB-ACCESS-SIGN
header is generated by creating an HMAC-SHA-256 using the secret key on the prehash string timestamp + method + requestPath + body
(where +
represents string concatenation) and Base64-encode the output.
timestamp
is the same as the CB-ACCESS-TIMESTAMP
header.
method
should be UPPER CASE, e.g., GET
or POST
.
requestPath
should only include the path of the API endpoint. Do NOT include the base URL or query parameters when creating the signature.
Valid requestPath example to include in the string for hashing:
body
is the request body string or omitted if there is no request body (typically for GET
requests).