Getting Started
Rate Limiting
Rate Limiting
The GG365 Golf API enforces rate limits per endpoint to ensure optimal performance for all users.
Rate Limits by Endpoint Type
| Endpoint Type | Rate Limit | Description |
|---|---|---|
| Course data | 100 requests/min | Course search, details, pricing, terms |
| Availability | 20 requests/min | Tee time availability checks |
| Bookings | 10 requests/min | Create, update, cancel bookings |
Premium partners may receive higher rate limits. Contact your account manager for details.
Response Headers
Rate limit information is included in response headers:
Code
| Header | Description |
|---|---|
X-RateLimit-Limit | Max requests allowed in the current period |
X-RateLimit-Remaining | Requests remaining in the current period |
X-RateLimit-Reset | Unix timestamp when the limit resets |
Rate Limit Exceeded
When you exceed your rate limit, the API returns 429 Too Many Requests:
Code
Best Practices
- Cache course data (courses and pricing change infrequently)
- Batch date range queries instead of individual date calls
- Use exponential backoff when retrying after rate limit errors
- Monitor usage via response headers
Last modified on