Scraper Data Set History V4

• Authorization: Header
  HashScraper API key. Send it in the form Bearer <api_key>.

  Example Bearer YOUR_API_KEY
• schedule_id: String (path)
  ID of the scraper to query. Passed as the {schedule_id} path segment. You can copy the Bot ID from Actions → Copy Bot ID on the scraper's detail page.

  Example 8f3a7c1e9b5d24f6
• sorting: optional String
  Sort direction by data set ID. Do not change mid-pagination — the cursor direction flips with it.

  Default asc Allowed asc, desc
• cursor: optional Integer
  Pass the response's next_cursor back to fetch the next page. Applied in the current sorting direction.
• sr_status: optional String
  Filter to data sets in this status. One of canceling, canceled, finish, ready, retry, running, complete.

  Allowed canceling, canceled, finish, ready, retry, running, complete
• limit: optional Integer
  Maximum data sets per page.

  Default 100 Allowed 1 ~ 1000

• result: String
  Result of the request.

  Allowed success, error
• version: String
  API version.

  Example v4
• request_id: String
  Request trace ID.

  Example req_5a8c1f1c-...
• elapsed_sec: Float
  Time the server took to produce the response, in seconds (Float).

  Example 0.0142
• count: Integer
  Number of data sets in this response.
• next_cursor: Integer | null
  Pass back as cursor on the next call. null means this is the last page.
• schedule: Object
  Context of the queried scraper (returned identically across pages).

  • id: String
    Echo of the scraper ID.
  • name: String
    Scraper name.
  • latest_schedule_result_id: Integer | null
    Most recent data set ID for this scraper. null when the scraper has no data sets yet.
• data: Array<Object>
  Array of data sets.

  • schedule_result_id: Integer
    Data set ID.
  • sr_status: String
    Collection status. Typically one of ready, running, retry, finish/complete, canceling (cancel in progress), canceled (cancel finished). Some legacy data sets may return locale-translated labels (e.g. Korean '완료'/'처리중'/'취소'/'중지' or English Complete/Processing/Cancel/Stop).
  • data_count: Integer
    Number of results collected in this data set. While the data set is in progress this is real-time and may increase between polls.
  • created_at: String (ISO 8601)
    Data set creation time (ISO 8601, Asia/Seoul).
  • updated_at: String (ISO 8601)
    Data set last update time (ISO 8601, Asia/Seoul). Updated frequently by the worker during collection, and typically stays constant after completion.
  • param_info: Object
    Snapshot of the parameters used for this data set. Keys are stable (param1~paramN) and each entry contains name (label) and value.
  • union: Boolean | null
    Whether union mode is enabled. Union mode reuses the scraper's last data set instead of creating a new one, accumulating results inside it. Reflects the union value recorded at the time this collection ran.

Error Responses

• MISSING_API_KEY
  Missing or malformed Authorization header. Send as Authorization: Bearer <api_key>. (HTTP 401)

  {
    "result": "error",
    "version": "v4",
    "request_id": "req_5a8c1f1c-...",
    "code": "MISSING_API_KEY",
    "message": "API key is missing.",
    "elapsed_sec": 0.0008,
    "details": { "hint": "Send `Authorization: Bearer <api_key>` header." }
  }

• INVALID_API_KEY
  No user matches the provided API key. (HTTP 401)

  {
    "result": "error",
    "version": "v4",
    "request_id": "req_5a8c1f1c-...",
    "code": "INVALID_API_KEY",
    "message": "API key is invalid.",
    "elapsed_sec": 0.0011
  }

• SCHEDULE_NOT_FOUND
  No scraper matches the ID, or the caller does not have access. (HTTP 404)

  {
    "result": "error",
    "version": "v4",
    "request_id": "req_5a8c1f1c-...",
    "code": "SCHEDULE_NOT_FOUND",
    "message": "Schedule not found.",
    "elapsed_sec": 0.0021,
    "details": { "resource": "schedule", "id": "8f3a7c1e9b5d24f6" }
  }

• INVALID_PARAM (sorting)
  sorting must be asc or desc. (HTTP 400)

  {
    "result": "error",
    "version": "v4",
    "request_id": "req_5a8c1f1c-...",
    "code": "INVALID_PARAM",
    "message": "Invalid sorting parameter.",
    "elapsed_sec": 0.0014,
    "details": { "param_name": "sorting", "allowed": ["asc","desc"] }
  }

• INVALID_PARAM (sr_status)
  sr_status is not one of the allowed values. (HTTP 400)

  {
    "result": "error",
    "version": "v4",
    "request_id": "req_5a8c1f1c-...",
    "code": "INVALID_PARAM",
    "message": "Invalid sr_status parameter.",
    "elapsed_sec": 0.0014,
    "details": { "param_name": "sr_status", "value": "unknown", "allowed": ["canceling","canceled","finish","ready","retry","running","complete"] }
  }

Related Guides

• Collect Status V4
• Scrapers V4
• Storage V2