List Datasets V2

• api_key: String
  HashScraper API key

  Example YOUR_API_KEY
• schedule_id: String
  ID of the scraper to query.

  Example YOUR_SCHEDULE_ID
• page: optional Integer
  Page number to retrieve.

  Default 1
• sorting: optional String
  Sort direction by dataset creation time.

  Default asc Allowed asc, desc
• schedule_result_id: optional Integer
  Pass to inspect a specific dataset. Can be combined with other filters.
• sr_status: optional String
  Filter the result by collection status.

  Allowed ready, running, retry, finish, canceling, canceled

• result: String
  Request outcome.

  Allowed success, error
• version: String
  API version.

  Example v2
• current_page: Integer
  Current page number. Matches the page value sent in the request.
• total_page: Integer
  Total pages after filters.
• dataset: Array<Object>
  Array of datasets.

  • schedule_result_id: Integer
    Dataset ID. Pass it to other endpoints as schedule_result_id.
  • sr_status: String
    Current collection state. The values you typically receive are ready (queued), running, retry, finish, canceling (cancel in progress), and canceled (cancel finished). Some legacy datasets may return a Korean label instead.
  • created_at: String (ISO 8601)
    Dataset creation timestamp (ISO 8601, Asia/Seoul).
  • data_count: Integer
    Number of records collected in this dataset. This is a cached counter — records added very recently may not be reflected immediately.
  • sum_point: Integer
    Cumulative credits charged for this dataset's collection.
  • param_info: Object
    Snapshot of the parameters used when this dataset was collected. Only param1~param5 that were enabled are included, and keys carry the parameter labels (e.g. param1(keyword)). When the scraper has no label configured, the label slot may be empty (param1()) or a placeholder (param1(param1)).
  • no_result: Boolean | null
    Snapshot of the scraper's "no result" handling setting. May be null if the snapshot is missing or unparseable.
  • union: Boolean | null
    Snapshot of the scraper's union-result setting. May likewise be null.
• elapsed_time: Float
  Server-side processing time (seconds, as a numeric value).

  Example 0.0234

Error Responses

• schedule_id missing
  Required parameter schedule_id was not provided.

  {
    "result": "error",
    "version": "v2",
    "message": "`schedule_id` parameter is required"
  }

• Schedule not found
  No scraper matches the provided schedule_id, or it is not accessible.

  {
    "result": "error",
    "version": "v2",
    "message": "schedule(id: YOUR_SCHEDULE_ID) not found"
  }

• Schedule result not found
  The provided schedule_result_id does not exist within the given scraper.

  {
    "result": "error",
    "version": "v2",
    "message": "schedule_result(id: YOUR_SCHEDULE_RESULT_ID) of schedule(id: YOUR_SCHEDULE_ID) not found"
  }

• Invalid page
  page must be an integer.

  {
    "result": "error",
    "version": "v2",
    "message": "올바른 page 값을 넣어주세요. page: ..."
  }

• Invalid sorting
  sorting must be asc or desc.

  {
    "result": "error",
    "version": "v2",
    "message": "올바른 `sorting` 값을 넣어주세요(`asc` or `desc`). sorting: ..."
  }

• Invalid sr_status
  sr_status must be one of ready, running, retry, finish, canceling, or canceled.

  {
    "result": "error",
    "version": "v2",
    "message": "올바른 sr_status를 입력해주세요. sr_status: ..."
  }

• No dataset found
  Returned when no dataset matches the filters. The response is an error, not an empty success.

  {
    "result": "error",
    "version": "v2",
    "message": "조건에 맞는 데이터셋을 찾을 수 없습니다. schedule_id: ... | page: ... | schedule_result_id: ... | sr_status: ..."
  }

Related Guides

• Scrapers
• Collect Status
• Data V2
• Data V3
• All Data of Bot V2
• All Data of Bot V3