Entity Sport · Rate Limits

Entitysport Rate Limits

Entity Sport authenticates every Cricket API V2 request with a short-lived access token obtained from /auth, and access is gated by subscription plan and tournament coverage rather than published per-endpoint rate limits. Specific request-per-minute, daily-call, or concurrency limits are not documented publicly and are not reconciled in this artifact.

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

It captures 4 rate-limit definitions, measuring tournaments, token, and requests.

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

Tagged areas include Sports Data, Cricket, Live Scores, Fantasy, and Odds.

4 Limits Throttle: 429
Sports DataCricketLive ScoresFantasyOddsRate LimitingQuotasThrottling

Limits

Plan Tournament Coverage account
tournaments
see plan
Accessible competitions and depth depend on the subscribed plan tier.
Access Token Lifetime account
token
short-lived
Tokens expire (token_expires); clients must re-authenticate via POST /auth.
Daily / Per-Minute Call Limits account
requests
see provider documentation
Per-plan call quotas are not documented publicly; confirm with sales.
Live Endpoint Polling account
requests
see provider documentation
Recommended polling frequency for live/ball-by-ball endpoints is not published.

Policies

Token Authentication
Obtain a short-lived token from POST /auth and pass it as the token query parameter on all requests.
Tiered Access
Coverage and data depth scale with the subscribed plan; higher tiers unlock more tournaments and features.
Backoff Strategy
Clients should implement retry with backoff and re-authenticate when the access token expires.

Sources