Errors & limits
Categorize errors correctly, observe limits and fix integration problems.
On this page
Error responses
Using API errors application/problem+json with code, detail and requestId. Keep the request ID for diagnosis. The SDK places it in RebilixApiException Ready.
| HTTP | Procedure |
|---|---|
| 400 / 415 / 422 | Check the scheme, media type, mandatory fields or technical findings. |
| 401 / 403 | Check the key, expiration, environment and current creator permissions. |
| 404 | Control resource ID, workspace, environment, and artifact availability. |
| 409 | Differentiate error code: deviating idem power data, ongoing processing, changed testing or outdated retry counter. |
| 408 / 413 | Check upload time limit or file size. |
| 429 / 503 | Retry-after, resend the same data with the same Idempotency key. |
Size and processing limits
| Border | Value |
|---|---|
| JSON / XML / PDF | 1 MiB / 2,000,000 bytes / 10 MiB |
| Upload time limit | 30 seconds; set HTTP client for synchronous PDF processing to at least five minutes. |
| Per key and per minute | 60 requests / 5 processing POSTs |
| Per workspace / environment / minute | 300 requests / 20 processing POSTs |
| Parallelism | A maximum of two API processing operations per workspace/environment, four per process. |
| Open background contracts | 50 per workspace/environment |
| Interconnection IP | 120 requests per minute per instance. Behind a proxy, this limit can be shared. |
| History / Retry-JSON | Up to 100 entries per API page / 1 KiB Retry request |
Idempotence and safe repetition
Require document processing and job acceptance Idempotency-Key: 16–128 printable ASCII characters without spaces, for example a UUID. Save it with your ERP operation.
Same action, same normalized media type and exactly the same bytes provide the stored result. Idempotent-Replayed: true Shows the repetition. Modified data with the same key 409 idempotency_conflictA new key consciously starts a new process.
In case of: 409 request_in_progress Wait according to Retry-After. After process termination, a synchronous reservation can remain blocked for up to ten minutes. Job leases expire after 15 minutes; Webhook leases after two minutes. Workers must run for recovery.
/jobs/{id}/retry and /webhook-deliveries/{id}/retry Used expectedAttempts Reload at 409 and expressly decide to repeat it again.
Limiting Webhook Problems
| Symptom | Validate |
|---|---|
| No HTTP request | CaptureOnly? Worker active? Recipient created before graduation? Right environment? Order already terminal? |
| 401 in the ERP | Exact secret including whsec_, original bytes, full header and synchronized clock. |
| unsafe_destination | Public host; all resolved IPs must be allowed; no private addresses or redirects. |
| endpoint_inactive | Recipient deactivated or creator no longer authorized. Create replacement under an authorized account. |
| signing_key_unavailable | Rebilix operator must restore the appropriate data protection key bundle. |
| ERP receives duplicates | Expectable for repetitions. Use unique event ID and transactional inbox. |
| 2xx, but ERP remains unchanged | Check ERP inbox and own worker. 2xx confirms receipt, not completion of ERP processing. |
Check them out. Delivery history in the app or GET /webhook-deliveries/{id}Payload, HTTP status, and signature header of each attempt will help with the assignment.
Monthly working area quotas
HTTP 429 with workspace_allowance_exceeded means that the monthly quota for this action and environment has been reached. Usage & plan owners and administrators can check consumption and remaining units; this limit applies in addition to the short-term API rate limits.
Do not repeat immediately in a loop: resend the same request with the same Idempotency key after quota increase or change of month. Background orders check the quota at acceptance and processing; 202 does not reserve a monthly unit. If the quota is exhausted, the order remains for explicit repetition.
Successfully stored results are counted once, even if the test result is invalid or the conversion test is blocked. Technical errors without a result do not count. Generation and conversion test contain their internal checks. Conversion confirmation, downloads, idempotent repetitions and webhook deliveries do not count again. Live and Sandbox are separate. Reservations are valid for ten minutes; the month is set when booking in Europe/Berlin. Already approved processes can be completed within their reservation after a change of plan.