API ReferenceFetch

Fetch a URL (GET)

Direct HTTP fetch. Successful responses return the upstream response bytes verbatim; metadata is returned in X-Fetch-* headers. Non-2xx upstream responses use the `upstream_error` JSON envelope with the upstream HTTP status.

GET
/v1/fetch

Authorization

AuthorizationRequiredBearer <token>

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

In: header

Query Parameters

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"
curl https://api.bytekit.com/v1/fetch \
  -H "Authorization: Bearer sk_live_your_api_key_here"

Content from upstream.

"string"

Fetch

Fetch API — endpoints, requests, and responses.

POST /v1/fetchFetch 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`.