Limits and errors
Task and request limits
The API also applies request throttling:
120 requests per 60-second window for each source operation, including task
creation, per account. A throttled request returns 429 RateLimitExceeded
with Retry-After in seconds. Source and enrichment operation counters are
separate; the active-task limit below is shared.
| Limit | Value |
|---|---|
| Complete JSON request, including settings | 10 MiB (10,485,760 bytes) |
| Active tasks per account | Target of 20, shared with enrichment tasks |
| Execution deadline | 24 hours from creation |
| Retention | 90 days after completion, failure, or a stop |
List page size (limit) | 1–100; default 50 |
| Result response page | 128 KiB (131,072 bytes) |
| JSON nesting depth in settings | 10 levels |
| Objects returned by one source execution | At most 10,000 |
| Combined objects returned by one source execution | At most 5 MiB (5,242,880 bytes) |
| Each generated object | At most 16 KiB (16,384 bytes) |
Sources have no input array, so the enrichment input and batch limits do not apply. Source executions can continue in further steps: the per-execution output limits above are not a total task result cap or a guarantee of how many objects a source will generate. Tool settings can impose their own limits.
The account limit counts queued, running, and stop_asked ApiTasks whose
execution deadlines have not passed, across both task families and all API keys.
For example, 12 active enrichment tasks leave room for 8 source tasks.
Simultaneous requests can occasionally exceed the target of 20.
At the limit, creation returns 429 ActiveTaskLimitExceeded. Wait for a task to become completed, failed, or stopped before creating another. Asking it to stop does not immediately free its slot.
uniqueId is required: 1–128 ASCII letters, digits, underscores, or hyphens.
Active reservations are shared across both families. Settings follow the same
JSON constraints
as enrichment tasks, including undeclared settings. Follow a non-null
nextCursor even when a result page contains fewer objects than requested.
HTTP errors
Both APIs use the same HTTP error envelope and support references.
See the API error reference
for throttling, common API error codes, and response headers.
Authentication returns 401; missing permission 403; inaccessible/expired
tasks 404; active duplicate IDs or premature results 409; oversized
requests 413; invalid settings 422; and task or request limits 429.
Honor Retry-After when present.
Save X-Request-ID and any task error.traceId for support. Source failures
appear at task level, not inside generated objects. Retry reads with increasing delays and a retry limit. If a creation response was lost, check task history before trying again to avoid repeating paid work.