Skip to main content
Send your API Key in the API-Key header on every request. Keep your API Secret on your server to verify webhook signatures. It is never sent with a request.

API-Key Header

Include your API Key in the API-Key header for every API request:
  • You can find your API Key in your dashboard under Settings › API Keys.
  • Requests with a missing, invalid or revoked API-Key return 401 Unauthorized. A valid key used on a route its account type can’t access (for example, a sender key on a provider route) returns 403 Forbidden.
Do not commit your API keys to git, or use them in client-side code. Never share your API Secret. If you believe it has been compromised, rotate it immediately in your dashboard.

API Secret

Your API Secret is used for sensitive operations such as verifying webhook signatures and should never be shared or exposed in client-side code.
Keep your API Secret safe. The API Secret is for server-side use only (e.g., webhook signature verification). Never expose it in frontend code, public repositories, or logs.

Webhook Signature Verification

When receiving webhooks, use your API Secret to verify the authenticity of the payload. Refer to the webhook documentation for implementation details.
Always ensure your server verifies the SSL connection to Paycrest. Do not set SSL verification (e.g., VERIFY_PEER) to FALSE in your HTTP client.