Skip to main content

Overview

Every request to the Onboard Business API must include your API key and an HMAC-SHA256 request signature — there is no unsigned tier.
API keys used to call cash payment or crypto transfer endpoints must have IP whitelisting configured in the Business Dashboard. Requests from an unlisted IP are rejected. See Getting API Credentials.

Signing a request

Required headers for signed requests: The signature is computed over the timestamp and the exact JSON body you send, joined with &:
Include the computed values in your request headers:
Your timestamp must be within 30 seconds of the current time — if requests are unexpectedly rejected, check for clock drift on the machine generating the signature.
Unauthorized requests return a 401 status, whether the cause is a missing/invalid x-api-key or an invalid/expired signature. For example, a skewed timestamp returns:
Check the message field for the specific error.