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, in the API Commons Rate Limits shape.

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

Limit state is signalled in the retryAfter response header, and an exhausted limit returns HTTP 429.

This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.

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 Exhausted: HTTP 429 Quota: 429 retryAfter
Method: generated, dated 2026-05-16.
Written by API Evangelist on 2026-05-16 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
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.

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/discgolfapi-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.