Skip to main content
GET
Get Crawler Details
This endpoint retrieves detailed information about a specific crawler using its hash ID. It helps you understand each crawler’s availability, cost, parameters, and potential issues before using it.

Headers

string
required
Your API authentication token. Value: Token YOUR_API_KEY
string
default:"application/json"
Content type of the request. Value: application/json

Path Parameters

string
required
The unique identifier (hash/id) of the crawler. Example: 4734d096159ef05210e0e1677e8be823

Response Field Explanations

string
Unique identifier for the crawler. Example: "c106a44a98044ef18acc59986ae10967"
string
Human-readable name (e.g., “Google Maps Search Export”). Example: "Google Maps (1)"
string
URL-friendly identifier. Example: "google-maps-leads-scraper"
string
What the crawler collects, as shown in the store. Example: "Give us your properly built Google Maps Search URL(s). Grab all results available. Phone, rating, website included!"
string | null
Link to the crawler’s help article, or null when it has none. Example: null
integer | null
Position in the public store listing. null for crawlers that are not ranked. Example: 1
boolean
Whether the crawler is publicly accessible. Example: true
boolean
Whether the crawler is available for runs (false if paused). Example: true
boolean
Requires premium subscription or extra credits. Example: false
boolean
Currently experiencing issues (runs paused until fixed). Example: false
object | null
Required account sync details (null if no authentication needed). Example: null
array
Array of configurable parameters (task-level and squid-level). Example: []
array
Array of output field names this crawler collects. Example: []
integer
Maximum number of workers that can run this crawler in parallel. Example: 20
object
Credits charged per result row, keyed by plan type: current is the rate on today’s plans, legacy the rate kept by grandfathered subscriptions. Example: {"legacy": 1, "current": 1}
object
Credits charged per email found, keyed the same way as credits_per_row. Only meaningful for crawlers with an email enrichment function. Example: {"legacy": 100, "current": 2}
boolean
Whether this crawler can verify the email addresses it finds. Example: true
object | null
Throughput profile of the crawler’s default worker — success_ratio, min_rate_per_worker, and max_rate_per_worker. Used to project how long a run will take. null when no profile is published. Example: {"success_ratio": 1, "max_rate_per_worker": 200, "min_rate_per_worker": 100}
object | null
Same throughput profile for the email enrichment worker, which is typically slower and has a lower success ratio. null when the crawler has no email function. Example: {"success_ratio": 0.3, "max_rate_per_worker": 30, "min_rate_per_worker": 20}
array
Crawlers this one can chain into — each entry describes the target crawler, how its fields map from this crawler’s output (field_map), whether it autostarts by default, and the squid-level parameters it accepts. Empty when the crawler supports no chaining. See Configure Chain for a worked example.

Understanding Input Parameters

string
Parameter level: “task” (per URL/task) or “squid” (overall run behavior). Example: ""
string
For task-level: true indicates this parameter is used per task submission. Example: ""
string
For squid-level: true indicates this controls overall behavior or features. Example: ""
string
If true, this is an optional add-on feature with extra credit costs. Example: ""
string
Extra credits charged per row when this optional function is enabled. Example: ""
string
Parameter name to use when configuring the crawler. Example: "Google Maps (1)"
string
Data type of the parameter (string, int, boolean, etc.). Example: ""
string
Whether this parameter is mandatory. Example: ""
string
Default value if parameter is not provided. Example: ""
Check the ‘has_issues’ flag before creating tasks. If true, the crawler is experiencing problems and runs are paused.
Parameters with ‘function: true’ are optional add-ons that cost extra credits per row (specified in ‘credits_per_function’).
Some crawlers require account synchronization (see ‘account’ field). You’ll need to sync cookies before running these crawlers.
Use the ‘result’ array to know exactly what fields will be returned in your data. This helps you plan your data processing pipeline.

Code Examples

Response

200
The input and result arrays above are abridged. At the time of writing this crawler exposes 25 input parameters and 87 result fields — always read them from the live response rather than hard-coding them.