Verified BursaPay workflow: Understand API rate-limit tracking and how applications should respond to throttling.
1. Overview & Purpose
The gateway tracks request counts by API key or IP and exposes configurable rate-limit controls, including per-key overrides.
2. Requirements & Setup
Applications should handle 429 responses and retry with backoff.
3. Step-by-Step Workflow
- Track response status and retry headers where exposed.
- Back off after throttling instead of immediately repeating requests.
- Use batching or pagination rather than excessive polling.
- Request a controlled rate-limit override only when justified by workload.
4. Rules & Troubleshooting
Rate limiting is a safety control. Do not attempt to evade it by rotating IPs or creating unnecessary keys.
5. Verification & Next Steps
Build exponential backoff and bounded retries into integration clients.