Retry Data Set V4

POST www.hashscraper.com/v4/api/schedule_results/{id}/retry

Re-runs an existing data set with the same parameters.

Resets the requested data set to ready and re-queues it. The data set ID is reused (no new data set is created), so results accumulate within the same data set.

Retry is blocked while the data set is in an in-progress state (ready·running·retry·canceling) — you'll receive EXECUTION_BLOCKED with reason: already_running. Retry is only allowed from terminal states (finish/complete or other end states).

Ticket expiration and credit exhaustion block retry the same way they block a new collection.

Request Parameters

Authorization: Header

HashScraper API key. Send it in the form Bearer <api_key>.

Example Bearer YOUR_API_KEY
id: Integer (path)

ID of the data set to retry.

Example 239758028

Response Fields

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.0287
data: Object
Retry result.
- schedule_result_id: Integer
  
  Echo of the data set ID (same as requested).
- schedule_id: String
  
  ID of the scraper this data set belongs to.
- name: String
  
  Name of the scraper this data set belongs to.
- sr_status: String
  
  Status right after retry. Typically ready.
- 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.

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_RESULT_NOT_FOUND

No data set matches the ID, or the caller does not have access. (HTTP 404)

{
  "result": "error",
  "version": "v4",
  "request_id": "req_5a8c1f1c-...",
  "code": "SCHEDULE_RESULT_NOT_FOUND",
  "message": "ScheduleResult not found.",
  "elapsed_sec": 0.0021,
  "details": { "resource": "schedule_result", "id": "999999" }
}

EXECUTION_BLOCKED (already_running)

Data sets currently in progress cannot be retried. The block applies to the English codes (ready·running·retry·canceling) and to legacy data sets that store the equivalent Korean labels. (HTTP 409)

{
  "result": "error",
  "version": "v4",
  "request_id": "req_5a8c1f1c-...",
  "code": "EXECUTION_BLOCKED",
  "message": "Already running.",
  "elapsed_sec": 0.0017,
  "details": { "reason": "already_running", "sr_status": "running" }
}

TICKET_EXPIRED

The service ticket is expired or no ticket is registered. (HTTP 402)

{
  "result": "error",
  "version": "v4",
  "request_id": "req_5a8c1f1c-...",
  "code": "TICKET_EXPIRED",
  "message": "Service ticket expired",
  "elapsed_sec": 0.0033,
  "details": { "reason": "ticket_expired" }
}

CREDIT_EXHAUSTED

Available credits are exhausted; retry cannot start. (HTTP 402)

{
  "result": "error",
  "version": "v4",
  "request_id": "req_5a8c1f1c-...",
  "code": "CREDIT_EXHAUSTED",
  "message": "Credit exhausted",
  "elapsed_sec": 0.0033,
  "details": { "reason": "credit_exhausted" }
}

Related Guides

{
  "result": "success",
  "version": "v4",
  "request_id": "req_5a8c1f1c-9b2d-4e7c-9abf-3f7e0a4d1b21",
  "elapsed_sec": 0.0287,
  "data": {
    "schedule_result_id": 239758028,
    "schedule_id": "8f3a7c1e9b5d24f6",
    "name": "네이버 뉴스 검색",
    "sr_status": "ready",
    "param_info": {
      "param1": { "name": "키워드", "alias": "keyword", "value": "키성장" },
      "param2": { "name": "정렬",   "alias": "sorting", "value": "관련도순" }
    }
  }
}