Fetch Bulk
Fetch Bulk API — endpoints, requests, and responses.
For AI agents: https://bytekit.com/llms.txt — every docs page is available as markdown by appending .md
The Fetch Bulk API. 2 endpoints:
POST /v1/fetchFetch a URL (POST)
Same as GET /v1/fetch but with a JSON request body. The response is the same, including the `X-Fetch-Fast-Path` rule for what the body holds: the upstream bytes verbatim when it is `true`, the rendered page when it is `false`. **Limits:** request bodies are capped at 512 KB. An oversized body returns a `400` with error code `request_too_large`.
POST /v1/fetch/bulkBulk fetch URLs
Enqueues multiple URLs for HTTP fetching. Results delivered via webhook. Does not support options that require page rendering (wait_for_selector, etc.). Completion deliveries use `X-ByteKit-Event: bulk.completed` and the `BulkCompletedWebhook` contract: at most 500 complete items and 1 MiB, followed by cursor recovery through `GET /v1/fetch/bulk/{id}` whenever `recovery_required` is true. **Limits:** request bodies are guarded in a two-tier shape. A streamed body with no `Content-Length` header is capped at 2 MB before your API key is checked; a body that declares `Content-Length` is instead bounded there by a 20 MB fail-safe (not the real limit — see below), since that branch reads nothing until your key is verified. Once your key is verified, a second check re-gates the body against your account's own `max_bulk_size` (at this endpoint's per-item override budget), which reaches 16.8 MB for the largest documented account. A standard-plan account's effective ceiling is 2 MB; either tier's overrun returns a `400` with error code `request_too_large`.