Skip to main content
The RabbitPay API uses API keys to authenticate every request. Keys are created in the Dashboard and scoped per environment (test / live).

Base URL

All requests must be made over HTTPS. Plain HTTP requests are refused.

Bearer token

Pass your secret key as a Bearer token in the Authorization header:

Key types

Rotate any key that is committed to source control immediately from the Dashboard → Developers → API Keys → Roll.

Restricted keys

Restricted keys let you scope access to specific resources (e.g. read-only access to orders). Create them from Dashboard → Developers → Restricted keys.

Idempotency

All mutating requests (POST, PATCH, DELETE) accept an Idempotency-Key header. Sending the same key within 24 hours returns the original response instead of creating a duplicate resource.

Errors

RabbitPay returns standard HTTP status codes plus a JSON error body:

Rate limits

Default: 100 requests / second per API key. Response headers include:
Contact support@rabbitpay.ai to request a higher limit.