Skip to main content
GET
Get Crawler Parameters
This endpoint returns all configurable input parameters for a specific crawler. The response is organized into two main sections: task and squid.

Response Structure

The response contains:
  • task: Object containing task-level parameters (parameter name as key)
  • squid: Object containing squid-level parameters and functions
  • squid.functions: Optional add-on features with extra credit costs

Task-level Parameter Fields

string
Data type (string, int, boolean, etc.). Example: "string"
string
Logical grouping (e.g., “url”, “location”). Example: "url"
string
Validation pattern for string inputs. Example: "^https?://.*"
boolean
Whether the parameter is mandatory. Example: true
string | number | boolean | null
Default value if not provided. Example: null
string
Internal attribute name. Example: "url"
boolean
Whether it’s used for URL parameter generation. Example: true

Squid-level Parameter Fields

string
Data type of the parameter. Example: "string"
array
Array of valid values (for enum types). Example: ["en", "es", "fr"]
string | number | boolean | null
Default value if not provided. Example: "en"
boolean
Whether the parameter is mandatory. Example: false
string
Internal attribute name. Example: "language"

Functions (Optional Add-ons) Fields

integer
Display order of the function. Example: 1
boolean
Whether the function is enabled by default. Example: false
number
Extra credits charged per row when this function is enabled. Example: 0.5

Headers

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

Query Parameters

string
required
The unique identifier (hash/id) of the crawler. Example: 4734d096159ef05210e0e1677e8be823
The response structure uses parameter names as object keys. Access task parameters via params.task.url, squid parameters via params.squid.language, etc.
Functions under squid.functions are optional add-ons. Each function has a credits_per_function cost applied per result row when enabled.
Pay attention to ‘allowed’ arrays in squid parameters - these only accept specific values. Sending invalid values will cause validation errors.
Use ‘regex’ patterns in task parameters to validate input before sending. This helps catch errors early and reduces failed tasks.
Parameters with ‘group’ field are logically related. For location-based crawlers, you’ll typically need to provide all parameters in the ‘location’ group.

Code Examples

Response

200