Does the weclapp API have a rate limit?

Not as a fixed number. weclapp states that the API has no fixed rate limits. There is, however, a limit for parallel requests per tenant. Requests above it wait in a queue. After currently up to 30 seconds of waiting, the API responds with HTTP 429 Too Many Requests. The client must handle this error.

You don't get an error immediately. Requests above the limit are not rejected but wait until resources are free, and therefore take longer. Only when the wait time currently exceeds 30 seconds does HTTP 429 follow. So set client timeouts of at least one minute, so that requests that would succeed later don't abort too early.

In the API documentation, weclapp states no number for this (as of 11.10.2026), so we don't state one either. Treat the limit as unknown and design your client so that it can cope with wait times and 429. For bulk runs, start with a few parallel requests, increase step by step and watch the X-Weclapp-Wait-Ms header. Throttle when the wait time rises.

Catch the status code in the client, wait, retry the request and lengthen the wait on every further failed attempt (exponential backoff). weclapp names exactly this approach as a recommendation. For write requests, check before every retry whether the first attempt has already arrived. This is especially important after a client timeout or connection drop. It is our recommendation, not a requirement from weclapp.

Yes. With the X-Weclapp-Wait-Timeout-Ms header, you set how long a request waits at most for processing to start. X-Weclapp-Request-Timeout-Ms sets a limit for the entire request. Both headers can only shorten timeouts. The request timeout is a best effort, not a hard limit; the server ignores invalid or non-positive values.

weclapp recommends an event-driven architecture with webhooks and advises against unfiltered polling. If you do have to query, filter and fetch a few larger result sets instead of sending many individual requests. That lowers the effective request time and thus the load by which weclapp assesses.

The API documentation states no fixed number per minute, because weclapp sets no fixed rate limits (as of 11.10.2026). What matters is the number of concurrently active requests and the effective request time over several minutes. Many short requests are uncritical, many heavy requests over minutes can become critical. Watch X-Weclapp-Wait-Ms and throttle when the wait time rises.