GoalServe · Rate Limits

Goalserve Rate Limits

GoalServe gates feed access through registration, a unique per-account API access key carried in the request path, and IP whitelisting for in-play feeds, rather than publishing explicit RPM/RPS request quotas. Feeds are polled over HTTP GET on recommended refresh intervals (live scores every few seconds, live stats around every 30 seconds); excessive polling beyond documented refresh rates is discouraged. Specific numeric request limits are not reconciled in this artifact.

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

It captures 5 rate-limit definitions, measuring authentication, source_ip, refresh_interval, and staleness.

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

Tagged areas include Sports Data, Live Scores, Odds, Fixtures, and Soccer.

5 Limits Throttle: see provider documentation
Sports DataLive ScoresOddsFixturesSoccerRate LimitingQuotasThrottling

Limits

API Access Key account
authentication
one key per account
Feeds require a unique private API access key carried in the request path.
IP Whitelisting account
source_ip
whitelisted IPs only
In-play / inplay feeds require the caller's IP address to be whitelisted.
Live Score Polling feed
refresh_interval
every few seconds (recommended)
Live score feeds refresh every few seconds; poll on the recommended interval.
Live Stats Polling feed
refresh_interval
~30 seconds (recommended)
Live statistics feeds update roughly every 30 seconds.
In-Play Staleness feed
staleness
30 seconds
If updated_ts does not advance for more than 30 seconds, odds and matches are suspended.

Policies

Recommended Polling Intervals
Poll each feed at its documented refresh cadence; avoid over-polling beyond the published intervals.
Access Gating
Access is controlled via registration, per-account API key, and IP whitelisting for in-play feeds.

Sources