Run task synchronously and get dataset items
GET/v2/actor-tasks/:actorTaskId/run-sync-get-dataset-items
Run a specific task and return its dataset items.
The run must finish in 300 seconds otherwise the HTTP request fails with a timeout error (this won't abort the run itself).
You can send all the same options in parameters as the Get Dataset Items API endpoint.
Beware that it might be impossible to maintain an idle HTTP connection for an extended period, due to client timeout or network conditions. Make sure your HTTP client is configured to have a long enough connection timeout.
If the connection breaks, you will not receive any information about the run and its status.
To run the Task asynchronously, use the Run task asynchronously endpoint instead.
Request
Path Parameters
Task ID or a tilde-separated owner's username and task's name.
Example:janedoe~my-taskQuery Parameters
Optional timeout for the run, in seconds. By default, the run uses a timeout specified in the task settings.
Example:60Memory limit for the run, in megabytes. The amount of memory can be set to a power of 2 with a minimum of 128. By default, the run uses a memory limit specified in the task settings.
Example:256Specifies the maximum number of dataset items that will be charged for pay-per-result Actors.
This does NOT guarantee that the Actor will return only this many items.
It only ensures you won't be charged for more than this number of items.
Only works for pay-per-result Actors.
Value can be accessed in the actor run using ACTOR_MAX_PAID_DATASET_ITEMS environment variable.
1000Specifies the Actor build to run. It can be either a build tag or build
number. By default, the run uses the build specified in the task
settings (typically latest).
0.1.234Specifies optional webhooks associated with the Actor run, which can be used to receive a notification e.g. when the Actor finished or failed. The value is a Base64-encoded JSON array of objects defining the webhooks. For more information, see Webhooks documentation.
Example:dGhpcyBpcyBqdXN0IGV4YW1wbGUK...Format of the results, possible values are: json, jsonl, csv,
html, xlsx, xml and rss. The default value is json.
jsonIf true or 1 then the API endpoint returns only non-empty items and
skips hidden fields
(i.e. fields starting with the # character).
The clean parameter is just a shortcut for skipHidden=true and
skipEmpty=true parameters.
Note that since some objects might be skipped from the output, that the
result might contain less items than the limit value.
falseNumber of items that should be skipped at the start. The default value
is 0.
0Maximum number of items to return. By default there is no limit.
Example:99A comma-separated list of fields which should be picked from the items,
only these fields will remain in the resulting record objects.
Note that the fields in the outputted items are sorted the same way as
they are specified in the fields query parameter.
You can use this feature to effectively fix the output format.
Example:myValue,myOtherValueA comma-separated list of fields which should be omitted from the items.
Example:myValue,myOtherValueA comma-separated list of fields which should be unwound, in order which they should be processed. Each field should be either an array or an object.
If the field is an array then every element of
the array will become a separate record and merged with parent object.
If the unwound field is an object then it is merged with the parent object
If the unwound field is missing or its value is neither an array nor an object and therefore cannot be merged with a parent object then the item gets preserved as it is.
Note that the unwound items ignore the desc parameter.
myValue,myOtherValueA comma-separated list of fields which should transform nested objects into flat structures.
For example, with flatten="foo" the object {"foo":{"bar": "hello"}}
is turned into {"foo.bar": "hello"}.
The original object with properties is replaced with the flattened object.
Example:myValueBy default, results are returned in the same order as they were stored.
To reverse the order, set this parameter to true or 1.
trueIf true or 1 then the response will define the Content-Disposition: attachment header, forcing a web browser to download the file rather
than to display it. By default this header is not present.
trueA delimiter character for CSV files, only used if format=csv. You
might need to URL-encode the character (e.g. use %09 for tab or %3B
for semicolon). The default delimiter is a simple comma (,).
;All text responses are encoded in UTF-8 encoding. By default, the
format=csv files are prefixed with
the UTF-8 Byte Order Mark (BOM), while json, jsonl, xml, html
and rss files are not.
If you want to override this default behavior, specify bom=1 query
parameter to include the BOM or bom=0 to skip it.
falseOverrides default root element name of xml output. By default the root
element is items.
itemsOverrides default element name that wraps each page or page function
result object in xml output. By default the element name is item.
itemIf true or 1 then header row in the csv format is skipped.
trueIf true or 1 then hidden fields are skipped from the output,
i.e. fields starting with the # character.
falseIf true or 1 then empty items are skipped from the output.
Note that if used, the results might contain less items than the limit value.
Example:falseIf true or 1 then, the endpoint applies the
fields=url,pageFunctionResult,errorInfo
and unwind=pageFunctionResult query parameters. This feature is used
to emulate simplified results provided by the
legacy Apify Crawler product and it's not recommended to use it in new
integrations.
falseIf true or 1 then, the all the items with errorInfo property will be
skipped from the output.
This feature is here to emulate functionality of API version 1 used for
the legacy Apify Crawler product and it's not recommended to use it in
new integrations.
falseStatus 201
Response Headers
- X-Apify-Pagination-Offset
- X-Apify-Pagination-Limit
- X-Apify-Pagination-Count
- X-Apify-Pagination-Total
{}
Schema
- object object
Status 400
Response Headers
{
"error": {
"type": "run-failed",
"message": "Actor run did not succeed (run ID: 55uatRrZib4xbZs, status: FAILED)"
}
}
Schema
error object required
- type string requiredExample:
run-failed - message string requiredExample:
Actor run did not succeed (run ID: 55uatRrZib4xbZs, status: FAILED)
- type string requiredExample:
Status 408
Request Timeout: the HTTP request exceeded the 300 second limit
Response Headers
{
"error": {
"type": "run-failed",
"message": "Actor run did not succeed (run ID: 55uatRrZib4xbZs, status: FAILED)"
}
}
Schema
error object required
- type string requiredExample:
run-failed - message string requiredExample:
Actor run did not succeed (run ID: 55uatRrZib4xbZs, status: FAILED)
- type string requiredExample: