GolfGlobe365 GAMP
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 TypeRate LimitDescription
Course data100 requests/minCourse search, details, pricing, terms
Availability20 requests/minTee time availability checks
Bookings10 requests/minCreate, 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
X-RateLimit-Limit: 100 X-RateLimit-Remaining: 98 X-RateLimit-Reset: 1720000000
HeaderDescription
X-RateLimit-LimitMax requests allowed in the current period
X-RateLimit-RemainingRequests remaining in the current period
X-RateLimit-ResetUnix timestamp when the limit resets

Rate Limit Exceeded

When you exceed your rate limit, the API returns 429 Too Many Requests:

JSONCode
{ "error": { "code": "rate_limit_exceeded", "message": "Rate limit exceeded. Please retry after 45 seconds.", "retryAfter": 45 } }

Best Practices

  1. Cache course data (courses and pricing change infrequently)
  2. Batch date range queries instead of individual date calls
  3. Use exponential backoff when retrying after rate limit errors
  4. Monitor usage via response headers
Last modified on