API Authentication
These order APIs identify merchants with X-Bolt-Key and verify requests using a timestamp and HMAC-SHA256 signature. Keep your API Key and Webhook secret on your server, outside frontend code, public repositories and logs.
Authentication Rules
- GET /api/v1/ping requires only X-Bolt-Key, with no timestamp or signature. It does not verify wallet configuration or callback delivery.
- Create, query and resend endpoints also require X-Bolt-Timestamp and X-Bolt-Signature. Use Unix milliseconds within 5 minutes of the server clock.
- The API Key identifies your account. HMAC uses the secret in your merchant Webhook configuration; these credentials are not interchangeable.
- Send the complete API Key, not the masked dashboard value. Update server configuration after resetting the API Key or Webhook secret.
01. API Key Header
HTTP Headers02. Integration Environment
Operational PolicyReal on-chain payments
These order endpoints receive mainnet assets on the selected network and do not provide a simulated-payment sandbox. Test API connectivity and callback verification separately first; an actual transfer is required for an on-chain payment.
Suggested testing order
Check your API Key with GET /api/v1/ping, then use the Webhook tester to verify signatures and idempotency. To test real payments, create an order meeting the minimum amount and pay the full returned amount. Resend notifications for confirmed or completed orders when needed, without repeating fulfillment.
Open Webhook tester →