Pinnacle API access: get a key, prove the first request.

Choose your access route

Official Pinnacle access and a third-party odds-data subscription are different arrangements. Pinnacle’s current API page offers bespoke applications for business, individual and academic use cases, subject to approval and eligibility. If you require an official contractual relationship or account-specific operations, start with Pinnacle’s own application route. A third-party subscription is not a Pinnacle account or an official-access guarantee. Checked September 26, 2026.

For a third-party integration, first read the coverage boundaries and choose a plan based on the data you consume. Keys, checkout and plan management live in the same account panel.

Four steps to a verifiable first response

1. Confirm the offer. Ask the service about your required sports, markets, transport and intended use, including any redistribution. Save the plan and terms you accept.
2. Create the account through the access link. Follow the current signup and verification steps, and keep the confirmation email and plan terms for your records.
3. Keep the key on your server. Store it in the ODDS_API_KEY environment variable. Never paste it into a public playground, put it in browser JavaScript or commit it to a repository. Send it in the documented x-portal-apikey request header.
4. Request one snapshot and validate the envelope. A successful status is only the first check. Require the documented object structure and an events array, then distinguish an empty result from malformed data.

These steps follow the current documentation, checked September 26, 2026.

Authentication is not the same as entitlement

A valid key can still lack the requested transport. REST snapshots, SSE alerts and raw WebSocket have different plan requirements. Before treating a connection error as a parser problem, confirm the account’s current subscription, add-ons and concurrent-connection policy.

Stop on authentication or permission errors and inspect the account. Do not retry an invalid key in a tight loop. On rate limits, respect Retry-After when provided; when the exhausted quota window is unknown, stop and investigate. A retry should consume a bounded time and attempt budget. Log the status and error code, never the key or a full server error body.

Trial and demo terms

The free tier does not expire: 20 requests per minute and 100 requests per day, no card, and the API key doubles as the account login. For stream evaluation, a three-day full demo with SSE, raw WebSocket and 10 requests per second is available on request. Confirm current entitlements on the account before depending on them. Checked September 26, 2026.

Start without buying access

The free key costs nothing and does not expire. Use it to confirm your runtime, parser and error messages against real responses before spending anything. When you move to a paid plan, treat the first response on the new entitlement as a fresh validation step: free-tier success does not establish streaming access, latency or the exact markets you will buy.