Official Pinnacle API rate limits

Answer: The official Pinnacle API README (opened 10 November 2026) states that access is restricted to a maximum of 2 distinct IP addresses per client, and that odds endpoints are limited to 1 request per 2 minutes, per endpoint, per sportId. Requests over that limit return HTTP 429 with code TOO_MANY_REQUESTS. The /sports call must be at most once every 60 minutes. The /line endpoint must not be called in a loop — it is for checking a price before placing a bet. Public access to that suite has been closed since 23 July 2025.

Those rules apply to Pinnacle's own API if you are approved. They are not PinnFeed's limits.

PinnFeed is a different product#

On PinnFeed, REST is a per-key token bucket and the WebSocket is a push feed, so you are not polling every two minutes. Current self-serve caps: Free 1 req/s and 1,000/day; Hobby 2 req/s; Builder 10 req/s and 3 sockets; Pro 30 req/s and 10 sockets. Details: PinnFeed rate limits and docs/limits.

Do not copy official 429 handling onto a PinnFeed key, or PinnFeed caps onto an official client.

Plans#

Builder (€99/mo, VAT incl. where applicable) for the live + prematch WebSocket. 3-day trial; a card is required and it is charged after day 3 unless you cancel. Official application: api@pinnacle.com, also described on Pinnacle API access closed.

Educational content for adults (18+).

Questions people ask#

Does PinnFeed also cap you at two IPs?#

This page only repeats the official README. PinnFeed's documented caps are rate, daily quota and WebSocket connection counts, not a two-IP official-API rule.

Which official endpoints are rate-limited?#

The README lists /v1/odds, /v1/odds/special, /v1/odds/parlay, /v2/odds, /v1/line, /v1/line/special and /v1/line/parlay.

Is this educational content for adults?#

Yes (18+).