Scrape Status

curl -X GET https://scrape.st/web/scrape/scr_01HZX... \
  -H "x-api-key: YOUR_API_KEY"

{
  "scrape_id": "scr_01HZX...",
  "version": "1.0.0",
  "status": "pending"
}

{
  "scrape_id": "scr_01HZX...",
  "version": "1.0.0",
  "status": "completed",
  "url": "https://example.com",
  "data": {
    "markdown": "# Example Domain...",
    "metadata": { "title": "Example Domain", "status_code": 200 }
  }
}

GET

web

scrape

{id}

curl -X GET https://scrape.st/web/scrape/scr_01HZX... \
  -H "x-api-key: YOUR_API_KEY"

{
  "scrape_id": "scr_01HZX...",
  "version": "1.0.0",
  "status": "pending"
}

{
  "scrape_id": "scr_01HZX...",
  "version": "1.0.0",
  "status": "completed",
  "url": "https://example.com",
  "data": {
    "markdown": "# Example Domain...",
    "metadata": { "title": "Example Domain", "status_code": 200 }
  }
}

Poll an async scrape started via Scrape URL with mode: "async". Once the job completes, the full scrape envelope (same shape as a sync response) is returned.

Path Parameters

string

required

The scrape_id returned by the async scrape request.

Response

string

pending, completed, or failed. While pending, only the job ID, version, and status are returned.

object

The scrape result, present once status is completed.

object

Present when status is failed: { code, message }.

curl -X GET https://scrape.st/web/scrape/scr_01HZX... \
  -H "x-api-key: YOUR_API_KEY"

{
  "scrape_id": "scr_01HZX...",
  "version": "1.0.0",
  "status": "pending"
}

{
  "scrape_id": "scr_01HZX...",
  "version": "1.0.0",
  "status": "completed",
  "url": "https://example.com",
  "data": {
    "markdown": "# Example Domain...",
    "metadata": { "title": "Example Domain", "status_code": 200 }
  }
}

Scrape URL Map Site

Getting Started

Webhooks

Tracking

Keywords

Profile Tracking

OCR

X Queries

Telegram Queries

Web Queries

Telegram Notifications

Backfill

Health & Metrics

API Keys

Path Parameters

Response

​Path Parameters

​Response

Path Parameters

Response