Verified BursaPay gateway workflow: Explains the key/IP rate-limit tracking used by the gateway API.
1. Overview & Purpose
ApiRateLimit tracks a key or IP identifier, request count and its active time window.
2. Requirements & Setup
Applications should tolerate 429-style throttling behavior and avoid unnecessary burst retries.
3. Step-by-Step Workflow
- Monitor request volume.
- Implement client-side backoff where appropriate.
- Use pagination rather than repeatedly fetching large datasets.
- Investigate persistent throttling as a traffic-design issue.
4. Rules & Troubleshooting
Rate limiting protects shared gateway resources and can apply independently by key or IP.
5. Verification & Next Steps
Tune request patterns before raising infrastructure limits or changing application behavior.