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	Period	Description
Search endpoints	60 requests	per minute	Course search, availability search
Read endpoints	120 requests	per minute	Get course details, booking details
Write endpoints	30 requests	per minute	Create bookings, update bookings
List endpoints	20 requests	per minute	List all courses, list bookings

Response Headers

Rate limit information is included in the response headers:

Code
 
X-RateLimit-Limit: 60
X-RateLimit-Remaining: 58
X-RateLimit-Reset: 1620000000

• X-RateLimit-Limit: Maximum number of requests allowed in the current period
• X-RateLimit-Remaining: Number of requests remaining in the current period
• X-RateLimit-Reset: Unix timestamp when the rate limit will reset

Rate Limit Exceeded

When you exceed a rate limit, the API will return a 429 Too Many Requests response:

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

Best Practices

To avoid hitting rate limits:

1. Implement caching for frequently accessed data
2. Batch requests where possible instead of making many small requests
3. Exponential backoff when retrying after rate limit errors
4. Monitor your usage using the response headers

Burst Rates vs. Sustained Usage

Our rate limiting system differentiates between:

• Short bursts of API activity (allowed within reasonable limits)
• Sustained high-volume usage (may trigger additional throttling)

For high-volume integrations, please contact us to discuss your specific needs.