PINNACLE REST / BUILT INTO YOUR BACKEND
Pinnacle REST API,
sized to ship.
Pinnacle REST API rate limits decide how fresh your backend's market state can be. Work out the request rate and daily volume your Pinnacle odds API pipeline needs, then match the capacity before you wire in the feed.
Free REST access: no card, no expiry.
20 requests/minute ·
100/day.
5 sports · live boards · 1s interval
One board request returns every live event in a sport with all its lines, so the count follows sports, not fixtures. Five a second fits Core 10 with half its ceiling spare. Work through your own numbers on the capacity planning page.
YOUR APPLICATION OWNS THE STATE
One Pinnacle odds API feed in.
One system of your own.
Keep the odds API key on your backend. Fetch once, normalize the response and let every internal service read your own copy.
-
01 / INGEST
Schedule the pull.
Request event and market snapshots at a pace your plan supports. Budget for retries as well as the regular refresh.
scheduler → REST -
02 / NORMALIZE
Build your market state.
Map incoming data to your own schema. Apply freshness checks and retain the state your product needs.
response → your store -
03 / SERVE
Power your interfaces.
Give your dashboard, pricing model or internal service a consistent view through your own backend.
your store → your app
CAPACITY, WITHOUT A CREDIT COUNTER
Choose the Pinnacle API rate you need.
Paid REST plans raise the per-second rate limit and carry unlimited total request volume. Pick the ceiling your refresh schedule needs.
Core 10 + alerts
The same REST capacity, with a separate stream of drop alerts.
$149 / month
Monthly prices in USD. Raw WebSocket is a separate $99/month add-on on these plans. SSE and raw frames are different inputs.
BEFORE THE FIRST REQUEST
A cleaner integration
starts with the boundaries.
- Does one event equal one request?
- No. One board request returns every event in a sport with all its lines, and after the first call the since cursor returns only what changed. Count sports, phases and intervals, not fixtures.
- Can I call the API from the browser?
- Keep your key in a server-side application. Your frontend should use your own backend, without exposing the credential.
- Does capacity planning account for bursts?
- No. The math on capacity planning gives an evenly distributed rate. A batch sent all at once can exceed a per-second limit even if its average fits; rate limits and backoff covers the 429 handling.
- Do I need SSE to refresh my dashboard?
- REST supplies market snapshots on your polling schedule. Add SSE when you also need processed drop events as a separate input.
FIRST MILESTONE: ONE REAL RESPONSE
Make the feed part of your stack.
Get a free REST key. Inspect the response, map your schema and move to paid capacity when your pipeline is ready. Evaluating streams? The three-day full demo covers SSE, raw WebSocket and 10 req/s on request.