API Reference
API Rate Limits
To ensure a consistent experience for all users, the Waitlister API implements rate limiting. This page explains our rate limits and provides best practices for handling them in your applications.
Rate Limit Overview
Rate limits vary based on your plan and are applied separately for each endpoint. The limits are based on requests per minute (RPM) from a single API key.
Rate Limits by Plan
| Plan | Sign-up Endpoint | Log View Endpoint |
|---|---|---|
| Starter | No API access | No API access |
| Pro (Standard API) | 60 RPM | 200 RPM |
| Scale (Priority API) | 120 RPM | 400 RPM |
These limits help ensure:
- Consistent performance for all users
- Protection against accidental infinite loops
- Prevention of API abuse
Rate Limit Headers
When you make an API request, we include headers that provide information about your current rate limit status.
| Header | Description |
|---|---|
X-RateLimit-Limit | The maximum number of requests allowed per minute |
X-RateLimit-Remaining | The number of requests remaining in the current rate limit window |
X-RateLimit-Reset | The time at which the current rate limit window resets (Unix timestamp) |
For example:
X-RateLimit-Limit: 60
X-RateLimit-Remaining: 45
X-RateLimit-Reset: 1683741600
Increasing Your Rate Limits
If you need higher rate limits:
- Upgrade Your Plan: The Scale plan provides double the API rate limits of the Pro plan.
- Contact Support: For enterprise-level needs, contact us through the public contact form to discuss custom rate limits.
Monitoring Your API Usage
To prevent hitting rate limits, monitor your API usage regularly.
- Check rate limit headers in your API responses
- Implement logging of API calls and response headers
- Set up alerts when approaching rate limits
- Review your API usage patterns to identify optimization opportunities
By following these best practices, you can make sure your application interacts smoothly with the Waitlister API while respecting the rate limits.