Rate limits
Learn about Dub’s API rate limits.
Dub’s API rate limiting is in conformance with the IETF standard:
| Header Name | Description |
|---|---|
X-RateLimit-Limit | The maximum number of requests that the consumer is permitted to make per hour. |
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 in UTC epoch seconds. |
Retry-After | The number of seconds to wait before retrying the request again. |
Dub’s API is capped at 60 requests per minute per key on the Free plan, with elevated limits for Pro plan and above.
This is implemented to ensure a fair usage policy so that excessive use by a single user does not adversely affect the performance and usage of the API by others.
You’ll receive a 429 Too Many Requests response code if the rate limit is exceeded.
Rate limits by plan
Depending on your Dub.co plan, you can expect the following rate limits:
| Plan | Rate limit |
|---|---|
| Free | 60 requests per minute |
| Pro | 600 requests per minute |
| Business | 3,000 requests per minute |
| Enterprise | Custom – reach out to sales for details |
How to comply with rate limits
Here are some tips on how you can optimize your API setup to comply with our rate limits:
1. Bulk link creation
If you need to create a lot of links within a short period of time, try our bulk link creation endpoint instead (create up to 100 links in one API call)
2. Fetch workspace-level analytics
If you’re using our Analytics API, instead of retrieving the clicks count for every single link, try making a single API call to get workspace-level click analytics instead.
Alternatively, you can also periodically fetch a list of links sorted by last clicked, and paginate through the links until you get the one that has the same clicks value as the one you have stored – that way you know you’ve updated all the links that were clicked on since your last update.
Was this page helpful?