DEVELOPER DOCUMENTATION

Authenticate requests

Your first request, the API reference, and everything in between.

Get API key

One key. Every request.

Send your API key with every V2 request. Public league browsing on this website does not need a key.

Send your key in the request header

Add x-api-key to your API requests. New to the API? Follow the quickstart to create your account and key.

Request header
x-api-key: YOUR_API_KEY

Store your key on your server

Save the key as an environment variable, such as SPORT_API_KEY, and read it from your backend. Don’t bundle it into browser code, commit it to Git, or include it in a URL.

The endpoint reference lets you enter a key to try a request. Entered credentials are not saved between page reloads.

Allow your website’s origin

Requests from a browser carry the page’s origin, such as https://app.example.com. The API answers them only when that origin is listed on the key, and refuses the rest with 403. Requests from your server send no origin and are not affected.

Add origins with the globe button next to a key in Your API keys. Use the scheme and host only, with a port if it isn’t the default, for example http://localhost:3000. Changes apply to the next request.

An origin list stops other websites using your key in a browser, but anyone who loads your page can still read the key. Keep keys on your server where you can.

Manage and rotate your keys

Keys are shown once when created. Use a separate named key for each app or environment, and manage them in Your API keys.

To rotate a key, create a replacement, update your server environment, and then revoke the old key. Revocation takes effect on the next request.

If a key is lost or exposed, revoke it in your dashboard and create a replacement.