Run Actor synchronously with input and return output
POST/v2/acts/:actorId/run-sync
Runs a specific Actor and returns its output.
The POST payload including its Content-Type header is passed as INPUT to
the Actor (usually application/json).
The HTTP response contains Actors OUTPUT record from its default
key-value store.
The Actor is started with the default options; you can override them using various URL query parameters. If the Actor run exceeds 300 seconds, the HTTP response will have status 408 (Request Timeout).
Beware that it might be impossible to maintain an idle HTTP connection for a long period of time, 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 Actor asynchronously, use the Run Actor API endpoint instead.
Request
Path Parameters
Actor ID or a tilde-separated owner's username and Actor name.
Example:janedoe~my-actorQuery Parameters
Key of the record from run's default key-value store to be returned
in the response. By default, it is OUTPUT.
OUTPUTOptional timeout for the run, in seconds. By default, the run uses a timeout specified in the default run configuration for the Actor.
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 default run configuration for the Actor.
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 maximum cost of the run. This parameter is
useful for pay-per-event Actors, as it allows you to limit the amount
charged to your subscription. You can access the maximum cost in your Actor
by using the ACTOR_MAX_TOTAL_CHARGE_USD environment variable.
5Determines whether the run will be restarted if it fails.
Example:falseSpecifies 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 default run
configuration for the Actor (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...Bodyrequired
- object object
Status 201
Response Headers
{
"bar": "foo"
}
Schema
- object object
Status 400
Response Headers
{
"error": {
"type": "run-failed",
"message": "Actor run did not succeed (run ID: 55uatRrZib4xbZs, status: FAILED)\n"
}
}
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
Response Headers
{
"error": {
"type": "run-timeout-exceeded",
"message": "Actor run exceeded timeout of 300 seconds for this API endpoint"
}
}
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: