Rate Limits

The WedStay API uses rate limits to ensure fair usage and platform stability.

Tiers

All limits reset at midnight UTC.

Rate limit headers

Every API response includes rate limit information in the headers:

Example headers

HTTP/1.1 200 OK
X-RateLimit-Limit: 100
X-RateLimit-Remaining: 87
X-RateLimit-Reset: 1709078400

429 Response

When you exceed the rate limit, you'll receive a 429 Too Many Requests response:

{
  "error": {
    "type": "rate_limit_exceeded",
    "code": "too_many_requests",
    "message": "Rate limit exceeded. Please wait 45 seconds before retrying.",
    "request_id": "req_abc123",
    "doc_url": "https://www.thewedstay.com/developers/rate-limits"
  }
}

Best practices

1. Cache responses — Venue data changes infrequently. Cache search results for at least 5 minutes.
2. Use pagination — Don't fetch all venues at once. Use cursor and limit parameters.
3. Check headers — Monitor X-RateLimit-Remaining to avoid hitting limits.
4. Implement backoff — On 429 responses, wait for the Retry-After duration before retrying.
5. Batch where possible — Use search filters to get the data you need in fewer requests.