Limits and status
Standard read-request limits and known exceptions. Write and streaming operations have their own limits in the operation reference. This page is not a live service-status page.
Request limits
| Limit | Value |
|---|---|
| Request body | 16 KiB (413 REQUEST_TOO_LARGE) |
| Answer | 2 MiB; larger answers are 502 RESPONSE_TOO_LARGE, never truncated |
| Waiting for the PC (standard reads) | Up to 140 s in all; the PC has 120 s to execute |
| Requests in flight | 4 per organization (429 RELAY_BUSY) |
| Financial years per request | Up to 5, and no more than the plan covers |
| Credit-line stream | Up to 5 minutes and 64 MiB per stream |
These standard read-request figures may change with notice and apply regardless of plan or trial. Write and streaming operations can have different waiting, size and financial-year limits; check the operation you use.
Known limitations
- A live request needs the PC to be on and connected; otherwise it answers
503 DEVICE_OFFLINE. - A Cloud-mode answer reflects the last completed synchronization, not live data.
- One BUSY read runs at a time on the PC, so a long read can make the next one wait.