To ensure fair usage and protect the performance of the Vereinsantrag platform, we enforce rate limiting for all incoming API requests.â±ïž Rate Limit Policy#
Each client is subject to the following limits:20 concurrent requests (max number of requests handled simultaneously)2,000 requests per 10-minute windowThese rules apply globally and are automatically enforced by the system.| Limit Type | Value |
|---|
| Concurrent Requests | 20 |
| Fixed Window Limit | 2,000 requests per 10 minutes |
If your client exceeds any of these limits, the API will respond with:HTTP 429 Too Many RequestsA Retry-After header (in seconds) indicating how long to wait before retrying.
đ Handling Rate Limit Responses#
When your client exceeds the allowed limits, you'll receive a 429 Too Many Requests response. In this case:Respect the Retry-After header to determine when to try again.Avoid retrying immediately without a delay â this may lead to further rejections.If possible, implement exponential backoff or queuing in your client application.Example 429 Response#
HTTP/1.1 429 Too Many Requests
Retry-After: 120
Content-Type: text/plainToo many requests. Please try again later.đ Notes#
Limits apply per authenticated user (if available), or fall back to the request host if unauthenticated.These limits are global, affecting all routes in the API.No queuing is implemented â excess requests are immediately rejected. 