Sportmonks · Rate Limits

Sportmonks Rate Limits

Sportmonks enforces a per-entity hourly rate limit that scales by subscription plan. Each "entity" (fixtures, teams, players, livescores, etc.) gets its own bucket, so a client polling multiple entities does not exhaust a single shared pool. Every response includes a rate_limit object with the entity name, remaining requests, and reset window. The same limit applies regardless of whether the API token is presented via the Authorization header or the api_token query parameter.

Sportmonks Rate Limits is the machine-readable rate-limit profile for Sportmonks on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 5 rate-limit definitions, measuring requests_per_hour.

The profile also includes 4 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Football, Rate Limiting, and Sports Data.

5 Limits Throttle: 429
FootballRate LimitingSports Data

Limits

Free Plan — Per Entity api_key
requests_per_hour · hour
180
Free-plan ceiling per entity. Each entity (fixtures, livescores, teams, etc.) maintains its own counter.
Starter — Per Entity api_key
requests_per_hour · hour
2000
2,000 requests per hour per entity on the Starter plan.
Growth — Per Entity api_key
requests_per_hour · hour
2500
2,500 requests per hour per entity on the Growth plan.
Pro — Per Entity api_key
requests_per_hour · hour
3000
3,000 requests per hour per entity on the Pro plan.
Enterprise — Per Entity api_key
requests_per_hour · hour
5000
5,000 requests per hour per entity on the Enterprise plan.

Policies

Per-Entity Buckets
Counters are tracked separately for each entity (livescores, fixtures, teams, players, leagues, etc.). Heavy polling of one entity does not exhaust the budget for another.
Response Metadata
Every response includes a rate_limit object containing requested_entity, remaining, and resets_in_seconds. Clients should read these headers/body fields instead of polling blindly.
Trial Inherits Plan Limit
A 14-day trial uses the limits of the paid plan it was started against.
Header vs Query Token
Limits apply per API token; the auth placement (Authorization header vs api_token query parameter) does not affect the bucket.

Sources