API Documentation
Integrate RateMap data into your trading infrastructure. Use REST for broad compatibility and WebSocket for low-latency live updates.
Two ways to authenticate
Web users authenticate with a Bearer JWT. API clients can use the X-API-Key header where supported.
Web users
JWTPass the token in the Authorization header as a Bearer JWT.
API calls
API KeyUse the X-API-Key header for service-to-service access where enabled.
Core endpoints
These endpoints are the foundation for dashboards, alerting services, and batch analytics.
| Endpoint | Purpose | Notes |
|---|---|---|
GET GET /api/v1/rates/all | All exchange live rates | Realtime funding overview across tracked venues |
GET GET /api/v1/opportunities | Opportunity scanner | Cross-exchange arbitrage opportunities |
GET GET /api/v1/public/fri/current | Current FRI | Latest Funding Rate Index snapshot |
GET GET /api/v1/public/fri/history?days=7 | FRI history | Historical FRI series for charting |
Live streaming for Pro & Enterprise
Use the WebSocket stream when you need fast updates and lower latency than REST polling.
Empty arrays mean subscribe to everything.
The server sends {"type":"ping"} every 30 seconds. Reply with{"type":"pong"}. A connection that stays silent for 90 seconds is closed.
Use exponential backoff: 1s → 2s → 4s → 8s → 16s → 30s max.
1008: JWT invalid or missing4001: Permission denied4003: Permission denied
Download tick-level funding rate data for backtesting
Export historical funding data in JSON or CSV for research, modeling, and backtests.
| Parameter | Type | Description |
|---|---|---|
| exchange | string, optional | Exchange name, e.g. binance |
| symbol | string, optional | Trading pair, e.g. BTCUSDT |
| start_date | date, optional | Start date in YYYY-MM-DD format |
| end_date | date, optional | End date in YYYY-MM-DD format |
| limit | int, optional | Max rows. Pro up to 5000, Enterprise up to 10000 |
Parameters are the same as the JSON endpoint. The response returns text/csv, which is suitable for Excel or pandas imports.
| Plan | Limit | Range |
|---|---|---|
| Pro | Up to 5000 rows | Date range limited to 30 days |
| Enterprise | Up to 10000 rows | No date restriction |
Plan-based access
WebSocket access is included for higher tiers. REST access is rate-limited to protect the service.
| Plan | Limit | Notes |
|---|---|---|
| Free | No API access | REST polling only |
| Starter | 100 req/day | REST polling only |
| Pro | 1,000 req/day + WebSocket | Recommended for active trading workflows |
| Enterprise | Custom + WebSocket | Best for desks and internal tooling |
Common HTTP responses
These are the most common errors you will see while integrating RateMap APIs.
| Status | Meaning | Action |
|---|---|---|
| 401 | Missing or invalid JWT | Send a valid Bearer token in Authorization. |
| 403 | API key rejected or tier blocked | Check entitlement or use a higher plan. |
| 429 | Rate limited | Back off and retry with a lower request frequency. |
| 5xx | Server side error | Retry later or inspect service health. |
REST is the safest default. Use WebSocket for live dashboards, alert engines, and trade monitoring systems that need lower latency.