Get All Scraping Results of a Schedule V2

• api_key: String
  HashScraper API key

  Example YOUR_API_KEY
• schedule_id: String
  ID of the target scraper.

  Example YOUR_SCHEDULE_ID
• page: optional Integer
  Page number to retrieve. Do not combine with cursor pagination (next_id). When both are provided, the cursor filter is applied first and page is applied on top, which may yield unexpected results.

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

  Default asc Allowed asc, desc
• next_id: optional Integer
  Pass the next_cursor value from the previous response as-is.
• since: optional String
  Retrieve records created on or after the given time (inclusive). %Y-%m-%d %H:%M:%S format, Korea Standard Time.

  Example 2026-04-24 00:00:00

• result: String
  Request outcome.

  Allowed success, error
• version: String
  API version.

  Example v2
• data_count: Integer
  Number of items in this page.
• current_page: Integer
  Current page number. Matches the page value sent in the request.
• total_page: Integer
  Total number of pages. When next_id or since is applied, this reflects the filtered subset, not the entire dataset.
• min_id: Integer
  Minimum id among items in this page. Informational only — do not use for pagination.
• max_id: Integer
  Maximum id among items in this page. Informational only — do not use for pagination.
• next_cursor: Integer | null
  Pass this value as next_id on the next request. null indicates the last page.
• data: Array<Object>
  Array of scraping result records.

  • id: Integer
    Unique record identifier.
  • schedule_result_id: Integer
    ID of the dataset this record belongs to.
  • created_at: String (ISO 8601)
    Collection timestamp (ISO 8601, Asia/Seoul).
  • updated_at: String (ISO 8601)
    Last update timestamp (ISO 8601, Asia/Seoul). Scraped records are typically not modified, so this usually matches created_at.
  • <dynamic fields>: Any
    Dynamic fields. The set of keys depends on the scraper's result-column configuration.
• 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"
  }

• 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, desc) sorting: ..."
  }

• Invalid next_id
  next_id must be an integer.

  {
    "result": "error",
    "version": "v2",
    "message": "정수 타입의 next_id 값을 입력해주세요. next_id: ..."
  }

• Invalid since
  since could not be parsed as a valid timestamp.

  {
    "result": "error",
    "version": "v2",
    "message": "since 형식이 잘못되었습니다. since: ..."
  }

Related Guides

• Scrapers
• Storage
• All Data of Bot V3