About this endpoint
What it does
Creates one or more SERP Classic tasks based on the search queries submitted in the request body. If multiple queries are provided in the query array, a separate task is created for each one. The response returns an array of task objects, each representing a queued or in-progress task with its own id, echoed request parameters, and current status. An apikey is accepted as a query parameter for authentication.
Note: tasks are asynchronous — a newly created task will typically have is_completed: false and status: null until it finishes processing. Poll the task using its id via the task status/result endpoint to retrieve the final SERP data.
Request Body
| Parameter | Type | Mandatory | Description |
|---|---|---|---|
| query | String Array | Yes | Search queries to submit. One task is created per query. |
| device | String | Yes | Device type for the task. |
| location_id | Integer | Yes | Location identifier. |
| language_code | String | Yes | Language code for the task. |
| search_engine | String | Yes | Search engine to use. |
| tag | String | No | Optional task tag. |
Response
Returns an array of task objects — one per query submitted. Each object includes a server-generated id, the echoed task parameters, and status-tracking fields (is_completed, status, added). See Output Schema below for the full field-level breakdown.