DiscGolfAPI · Rate Limits

Discgolfapi Rate Limits

Machine-readable rate limit definitions for the DiscGolfAPI public API. Captures documented response codes for throttling, the fair-use policy, and the recovery semantics consumers should implement.

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

It captures 2 rate-limit definitions, across the free tier, measuring requests_per_minute and requests_per_month.

The profile also includes 5 backoff/retry policies defined and response codes documented for throttled, quotaExceeded, and serviceUnavailable.

Tagged areas include Disc Golf, Sports, Courses, Open Data, and Recreation.

2 Limits Throttle: 429 Quota: 429
Disc GolfSportsCoursesOpen DataRecreationRate LimitingFair Use

Limits

Public Free Tier Fair Use ip
requests_per_minute · minute
-1
No published numeric rate. -1 indicates "not specified by provider." Consumers should treat 429 responses as authoritative and back off.
Public Free Tier Monthly Volume ip
requests_per_month · month
-1
No published monthly quota. -1 indicates "not specified by provider."

Policies

Fair Use
Public endpoints are intended for apps, websites, maps, directories, and research. Cache responses where practical, avoid unnecessary repeated requests, and do not mirror or republish the full dataset as a competing service.
Backoff Strategy
Clients receiving a 429 Too Many Requests response should implement exponential backoff with jitter and honour any Retry-After header when present.
Excessive Automated Traffic
The provider documents that 429 may be returned when automated traffic is excessive. Automated clients should rate-limit themselves proactively rather than relying on server-side throttling.
Server Errors
Transient 500 responses may occur. Clients should retry idempotent reads with backoff and surface persistent failures to the operator.
Caching
Responses include a publish_version envelope field that supports consumer-side cache validation. The dataset manifest publishes content-addressable artefact metadata (SHA-256 + bytes) for bulk-download cache strategies.