Skip to main content
All production usage of Bebop’s APIs requires an API key. Without one, trading endpoints return widened demo-mode quotes and some endpoints are inaccessible entirely.

​
Obtaining an API Key

Request an API key through the Bebop support page. The team will provision a key and send it to you directly.

​
Passing Your API Key

For HTTP requests (RFQ, Aggregation, Trade History), pass source (your partner identifier) as a query parameter, and authenticate with either the source-auth query parameter or header:
YOUR_API_KEY = "YOUR_API_KEY"

# Option 1: query parameter
params = {"source": "your-partner-id", "source-auth": YOUR_API_KEY}

# Option 2: Authorization header
params = {"source": "your-partner-id"}
headers = {"Authorization": f"Bearer {YOUR_API_KEY}"}

​
What Requires Authentication

APIWithout keyWith key
Price APICannot connectFull access to real-time price streams
RFQ APIDemo mode - quotes are widened, heavily rate limited and not suitable for productionFirm, tight quotes ready for execution
Aggregation APIDemo mode - quotes are widened, heavily rate limited and not suitable for productionFirm, tight quotes ready for execution
Trade History APIPublic lookups by wallet address onlyFull access - filter by source to see trades attributed to your integration
Demo mode is useful for testing your integration flow end-to-end before going live, but the prices returned are not competitive.

​
Rate Limits

Rate limits apply per API key. If you have concerns about throughput for your use case, reach out via the support page.

​
Best Practices

Keep your API key secret. Do not expose it in client-side code, public repositories, or browser network requests. All Bebop API calls should be made from your backend. If you suspect your key has been compromised, contact the Bebop team immediately via the support page to rotate it.