Skip to main content
Most data endpoints accept an API key in the X-API-Key header. Generate keys from your dashboard.
The interactive Try playground on each API reference page uses the same X-API-Key header. Paste your key once in the playground auth panel.

Public endpoints (no API key)

These routes do not require authentication: You can still send an API key on search routes — it identifies your account for dashboard usage tracking but does not change search results.

Protected endpoints (API key required)

Invalid or missing credentials on protected routes receive 401.

Endpoint access by plan

Requests that exceed your plan’s endpoint access receive 403.

Whale tracked-event limits

Historical data depth

Paid tiers can request deeper history for crypto interval markets. Free tier requests to BTC/ETH Up/Down interval orderbooks are rejected with 403. Keep your API key confidential. Do not expose it in client-side code or public repositories.