Rate Limiting
To guarantee high availability and protect against volumetric attacks, MediBridgeX implements a strict distributed leaky bucket algorithm across our Edge infrastructure.
Rate Limit Headers
Every API response includes standard rate limit headers. Monitoring these headers allows your integration to implement intelligent exponential backoff before hitting the threshold.
Response Headers
1HTTP/1.1 200 OK2X-RateLimit-Limit: 10003X-RateLimit-Remaining: 9984X-RateLimit-Reset: 16984032005Retry-After: 0HTTP 429 Too Many Requests
If you exceed your allotted quota, the gateway drops connections at the Edge and returns a 429 Too Many Requests status. The response will explicitly include a Retry-After header denoting the exact number of seconds your client must halt execution.
| Tier | Requests per minute | Burst Allowance |
|---|---|---|
| Developer Sandbox | 60 | 10 |
| Production Standard | 1,000 | 250 |
| Enterprise Dedicated | Custom (SLA backed) | Custom |