API Reference
The HedgePayments API is organized around REST. Our API has predictable resource-oriented URLs, accepts JSON-encoded request bodies, returns JSON-encoded responses, and uses standard HTTP response codes and authentication.Base URL
All API requests should be made to:Authentication
All API requests require authentication via Bearer token:Products
The HedgePayments API is organized by product:SideBet API
Round-ups as a service
CoverPay API
BNPL payment processing
Bankroll API
Payment method & wallet
SideBet Endpoints
CoverPay Endpoints
Bankroll Endpoints
Common Endpoints
These endpoints work across all products:Response Format
All responses are JSON with a consistent structure: Success Response:HTTP Status Codes
Rate Limits
Idempotency
ForPOST requests, you can include an Idempotency-Key header to safely retry requests:
Webhooks
HedgePayments sends webhooks for important events. See the Webhooks Guide for setup instructions. Common Events:sidebet.roundup.processedsidebet.transfer.completedcoverpay.payment.createdcoverpay.payment.completedcoverpay.payment.failedbankroll.payment.completedbankroll.p2p.sentbankroll.card.created

