Skip to content

Get a PAT (token exchange)

A Personal Access Token (PAT) authorizes your MCP client against POST / GET /mcp. Exchange the same Sports API credentials you use for REST: client_id plus secret_key (or the alias client_secret in JSON).

Mint PATs from your backend, CI, or a secure shell using the examples below, not from MCP client configuration files.

Method / URLPOST https://<mcp-host>/api/v1/token
Content-Typeapplication/json
AuthNone (credentials in JSON body)
FieldRequiredDescription
client_idyesSports API client ID
secret_keyyesSports API secret (alias: client_secret)
labelnoOptional label for your records (string, max 256 characters)
{
"client_id": "YOUR_CLIENT_ID",
"secret_key": "YOUR_SECRET_KEY",
"label": "cursor-laptop"
}

Example with curl:

Terminal window
curl -sS -X POST "https://mcp.statscore.com/api/v1/token" \
-H "Content-Type: application/json" \
-d '{"client_id":"YOUR_CLIENT_ID","secret_key":"YOUR_SECRET_KEY","label":"ci-agent"}'

The server applies rate limiting per IP before parsing the body, then per client_id after validation.

{
"token": "<PAT>",
"expires_at": null,
"warning": "Save this token now. It will not be shown again."
}

The live API may return the warning in another language; treat it as a one-time display reminder.

  • token: shown once. Use Authorization: Bearer <PAT> on /mcp (see Connect a client).
  • expires_at: ISO timestamp or null if the PAT does not expire.
HTTPerrorMeaningWhat to do
400missing_fieldsMissing client_id or secret, or invalid JSON bodySend both credentials in JSON; check Content-Type
400invalid_labellabel is not a string or is longer than 256 charactersOmit label or shorten it
403invalid_credentialsOAuth probe failed (wrong ID/secret or API denied)Verify client_id and secret from your contract; retry from a trusted network
409tenant_slug_conflictAccount configuration conflict on the MCP sideContact STATSCORE support - not fixable from the client
502statscore_unavailableSTATSCORE OAuth/API unreachable or transport errorRetry with backoff; escalate if persistent
429rate_limit_exceededToo many exchange attempts (per IP or per client_id)Wait for the window to reset; avoid tight retry loops
500(varies)Server misconfigurationContact support with timestamp and request id if available

Responses never include secret_key.

Limits apply per rolling window. If you hit 429 often under normal integration load, contact STATSCORE support.

LimitDefaultApplies to
Token exchange window15 minutesPOST /api/v1/token
Token exchanges per IP30Per window
Token exchanges per client_id10Per window
/mcp request window1 minuteTool calls
/mcp requests120Per PAT per window (unauthenticated calls may be limited per IP)

Each successful POST /api/v1/token with the same client_id and secret can mint a new PAT. Update your MCP client configuration with the new token; older PATs may stay valid until they expire or are revoked.

Field / actionIntegrator view
expires_at: nullNo expiry is set on this PAT - treat it as long-lived and protect it like a password
expires_at: ISO timestampThe PAT stops working after that time - exchange again before expiry
RotationCall token exchange again, swap the PAT in Authorization, then retire the old token
RevokeThere is no self-service revoke in the public docs here - to invalidate a leaked or unused PAT, contact STATSCORE support

If CI or agents mint many PATs, revoke or rotate on a schedule so abandoned tokens do not linger.