Fetch a URL (POST)

Same as GET /v1/fetch but with a JSON request body. **Limits:** request bodies are capped at 512 KB. An oversized body returns a `400` with error code `request_too_large`.

Authorization

AuthorizationRequiredBearer <token>

API key. Manage keys from the dashboard at app.bytekit.com.

In: header

Request Body

application/jsonRequired

urlRequiredstring

Format: "uri"

countrystring

Default: "US"Pattern: "^[A-Z]{2}$"

timeout_msinteger

Default: 60000Minimum: 1000Maximum: 60000

cache_ttlstring | integer

How long a freshly fetched URL may be served from cache. 0 skips the cache read; cache-eligible fresh results are still written with the default 7-day TTL so later non-zero-TTL callers can HIT. Safety-classified WAF husks remain live-only and are not written. Accepts Nh (hours, up to 168h), Nd (days, up to 7d), or the integer 0. Examples: 0, 48h, 2d. Invalid values receive a 422 validation_error with an actionable message.

Default: "48h"

customobject

User-supplied JSON payload, base64-encoded into the X-Fetch-Custom response header so callers can correlate the response back to caller-side state (job IDs, batch metadata, etc.). Capped at 4096 UTF-8 bytes after JSON serialization. Does NOT affect cache-key inputs — two requests differing only in custom share the same cache slot.

Default: {}

curl -X POST https://api.bytekit.com/v1/fetch \
  -H "Authorization: Bearer sk_live_your_api_key_here" \
  -H "Content-Type: application/json" \
  -d '{"url":"https://example.com"}'

Content from upstream.

"string"

Fetch a URL (POST)

Authorization

Request Body

Response