Session limits and rate controls for concurrent browsers
Plan | Free | Developer | Startup | Scale |
---|---|---|---|---|
Max Concurrent Browsers | 1 | 25 | 100 | 250+ |
Session Creation Limit per minute | 5 | 25 | 50 | 150+ |
429 Too Many Requests
error. That means the request was effectively dropped.
For example, if you have a Developer plan (with a limit of 25 concurrent sessions) you can create up to 25 sessions in a 60 second window. If you try to create a 26th session within that window, it will be rate limited and return an HTTP 429 error.
To check the status of your rate limit, you can look at the headers of the response:
x-ratelimit-limit
- How many requests you can make.x-ratelimit-remaining
- How many requests remain in the time window.x-ratelimit-reset
- How many seconds must pass before the rate limit resets.retry-after
- If the max has been reached, this is the number of seconds you must wait before you can make another request. This is documented here.