Rate Limiting

Properly prepare for and handle rate limits

MeetBit rate limits requests made to the Public API to ensure fair and safe usage of the platform.

Rate Limits

We rate limit both on the Client level and the Tenant level. Requests made under each Client counts towards the Tenant’s total number of requests.

Level	Default Limit per Second
Tenant	10
Client	5

To increase client level rate limits, you may update this in the MeetBit Admin Panel under a Client’s settings. To increase your Tenant’s total rate limit, contact us at [e-mail]

Both valid and invalid requests count towards the rate limit.

Rate Limit Headers

We follow the the IETF standard to inform you of the current limit through response headers. Use these headers to properly throttle your requests.

RateLimit-Limit: 5
RateLimit-Remaining: 1
RateLimit-Reset: 1
Retry-After: 60

RateLimit-Limit · integer · required

Maximum number of requests allowed within a window.

RateLimit-Remaining · integer · required

Number of requests left within a window.

RateLimit-Reset · integer · required

Number of seconds left until limit resets.

Retry-After · integer

Number of seconds to wait before making another request. Only present when the request is already rate limited.

Handling Rate Limited Errors

429 Too Many Requests
Content-Type: text/plain
Retry-After: 60
Too many requests.

If you receive a 429 Too Many Requests error, try the request again after waiting for the number of seconds indicated by the Retry-After header returned in the rate limited error response. Do not immediately try the request again as this will result in an incrementally longer timeout each time and can lead to your client being suspended. If this happense, please contact [e-mail] for assistance.