API ReferenceRecordings

Get recording status

GET
/v1/recordings/{id}

Authorization

AuthorizationRequiredBearer <token>

API key. Obtain from POST /v1/account/api-keys.

In: header

Path Parameters

idRequiredstring
Pattern: "^rec_"
curl -X GET "https://api.bytekit.com/v1/recordings/string" \
  -H "Authorization: Bearer <token>"

Recording completed or failed.

{
  "id": "rec_01j9abc123",
  "status": "pending",
  "url": "string",
  "format": "mp4",
  "scenario": "scroll",
  "duration_requested": 0,
  "video_url": "string",
  "thumbnail_url": "string",
  "page_title": "string",
  "duration_actual_ms": 0,
  "file_size_bytes": 0,
  "credits_charged": 0,
  "error_code": "string",
  "error_message": "string",
  "created_at": "2019-08-24T14:15:22Z",
  "completed_at": "2019-08-24T14:15:22Z",
  "expires_at": "2019-08-24T14:15:22Z",
  "poll_url": "string"
}

Create a scrolling recording

Always async — returns 202. Poll via GET /v1/recordings/{id}.

Scrape a URL

Fetches and processes a URL, returning content in one or more formats wrapped in a ScrapeEnvelope. Simple requests use the HTTP fast-path (~500ms); complex requests (delay_ms > 0, cookies, custom headers, wait conditions) are routed to headless Chromium and return HTTP 202 (3-15s). When `webhook_url` is provided and the scrape is async, webhook deliveries include `X-RapidCrawl-Event: scrape.completed` or `X-RapidCrawl-Event: scrape.failed` so receivers can dispatch on the header without parsing the body shape.