Documentation Index
Fetch the complete documentation index at: https://docs.lobstr.io/llms.txt
Use this file to discover all available pages before exploring further.
This endpoint retrieves detailed information about a specific run using its hash ID. A run represents an execution instance of a squid’s tasks, tracking progress, status, and results.
Your API authentication token. Value: Token YOUR_API_KEY
Query Parameters
The unique identifier (hash) of the run. Example: 0393be3ea6f74986906153df1c3f9894
Response Field Explanations
Unique identifier of the squid run. Example: "0393be3ea6f74986906153df1c3f9894"
Type of returned object (always “run”). Example: "run"
Date and time when the run was initially created (ISO 8601). Example: "2025-02-04T10:26:50.847633"
Date and time when the scraping run started executing. Example: "2025-02-04T10:25:41.623683"
Date and time when the scraping run completed or stopped. Example: "2025-02-04T10:26:52.222239"
Duration of the scraping run as a formatted timedelta string. Example: "0:00:50.183300"
Total credits consumed during the run. Example: 50.1833
Origin of the run initiation (e.g., “user”, “schedule”). Example: "user"
Current status of the squid run (see statuses table). Example: "done"
Total number of results collected. Example: 40
Number of unique results collected. Example: 40
Indicates if the export was successfully generated. Example: true
Date and time when export was generated. Example: "2025-02-04T10:26:53.780636"
Reason indicating why the run finished (see done reasons table). Example: "tasks_done"
Additional description providing context for done_reason. Example: null
Identifier of the squid this run belongs to. Example: "e445405ef4ab41208ef7d29b92a1a9dd"
Scheduled date/time for the next execution (if recurring). Example: null
Whether this run was force-launched. Example: false
Number of times results have been exported. Example: 1
Whether the email delivery was completed. Example: false
Timestamp when email delivery completed. Example: null
Email verification status for delivery. Example: null
Shorthand flag indicating whether the run has completed (any terminal status). Example: true
Run Statuses
| Status | Phase | Description |
|---|
| PENDING | Waiting | Run is created and waiting to start execution |
| RUNNING | In Progress | Run is currently collecting data |
| UPLOADING | In Progress | Data collection is complete, now uploading/exporting results |
| PAUSED | In Progress | Run has been temporarily paused; it can resume or be aborted |
| ABORTED | Completed | Run was manually stopped before completion |
| DONE | Completed | Run finished all tasks and exported the results successfully |
| ERROR | Completed | Run failed due to an error |
Done Reasons
| Reason | Description |
|---|
| tasks_done | All assigned tasks completed successfully |
| aborted | Scraping run manually aborted by user |
| no_credits_left | No credits remaining |
| no_account_available | No available accounts; refresh required |
| no_accounts | No scraper-linked accounts available to initiate run |
| cookies_expired | Scraper-linked account cookies expired; renewal required |
| wrong_credentials | Account credentials invalid |
| checkpoint_reached | Account is blocked at a checkpoint (manual verification required) |
| otp_needed | OTP verification required; please re-sync accounts |
| limit_exceeded | Scraper-linked account limit exceeded |
| slots_limit_exceeded | Scraping slots limit exceeded |
| too_many_requests | Run stopped due to excessive requests |
| batch_wait | Current batch completed; awaiting timeout |
| deactivated | Run has been deactivated |
| maintenance_fees_not_paid | Maintenance fees for this custom module have not been paid |
| last_invoice_not_paid | Previous invoice payment pending |
| export_fix | Export regenerated successfully after previous failure |
Use the status field to track run progress. Poll this endpoint periodically for long-running scrapes.
The done_reason field provides insight into why a run ended - useful for debugging failed runs.
Runs with status ‘error’ or unexpected done_reasons may indicate account issues that need attention.
Code Examples
curl -X GET "https://api.lobstr.io/v1/runs/0393be3ea6f74986906153df1c3f9894" \
-H "Authorization: Token YOUR_API_KEY"
Response
{
"id": "0393be3ea6f74986906153df1c3f9894",
"object": "run",
"squid": "e445405ef4ab41208ef7d29b92a1a9dd",
"is_done": true,
"created_at": "2025-02-04T10:26:50.847633",
"started_at": "2025-02-04T10:25:41.623683",
"ended_at": "2025-02-04T10:26:52.222239",
"next_launch_at": null,
"duration": "0:00:50.183300",
"credit_used": 50.1833,
"origin": "user",
"force_launch": false,
"status": "done",
"export_done": true,
"export_count": 1,
"export_time": "2025-02-04T10:26:53.780636",
"email_done": false,
"email_time": null,
"email_verification": null,
"total_results": 40,
"total_unique_results": 40,
"done_reason": "tasks_done",
"done_reason_desc": null
}
{
"error": {
"message": "Run not found",
"type": "not_found_error",
"param": "run_hash"
}
}