---
title: "Run Actor synchronously and return key-value store record"
method: POST
path: "/v2/actors/{actorId}/run-sync"
tags: ["Actors/Actor runs"]
---

# Run Actor synchronously and return key-value store record

`POST /v2/actors/{actorId}/run-sync`

Runs a specific Actor and returns a key-value store record.

The POST payload including its `Content-Type` header is passed as `INPUT` to
the Actor (usually <code>application/json</code>).

The response contains the record stored under the `OUTPUT` key in the run's
default key-value store. This is a legacy approach that has been replaced by
the Actor [output object](https://docs.apify.com/platform/actors/development/actor-definition/output-schema#output-object-definition);
Actors aren't required to store a record under this key, so the response may
not contain any data. Use the `outputRecordKey` query parameter to return a
different record.

The Actor is started with the default options; you can override them using
various URL query parameters.
If the Actor run exceeds 300<!-- MAX_ACTOR_JOB_SYNC_WAIT_SECS --> 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](#/reference/actors/run-collection/run-actor) API endpoint instead.

## Path parameters

- `actorId` string, required

## Query parameters

- `outputRecordKey` string
- `timeout` number, double
- `memory` number, double
- `maxItems` number, double
- `maxTotalChargeUsd` number, double
- `restartOnError` boolean
- `build` string
- `webhooks` string, byte

## Request body

- object

## Response `201`

- object

## Other responses

- `400` — Bad request - invalid input parameters or request body.
- `401` — Unauthorized - authentication required or invalid token.
- `402` — Payment required - the user has exceeded their usage limit, does not have enough credits, or the request lacks authentication and payment credentials.
- `403` — Forbidden - insufficient permissions to perform this action.
- `404` — Not found - the requested resource does not exist.
- `408` — The HTTP request exceeded the timeout limit
- `415` — Unsupported media type - the Content-Encoding of the request is not supported.
- `429` — Too many requests - rate limit exceeded.

---

[API](https://skmtc.net/apify/apis/apify-api.md) · [All operations](https://skmtc.net/apify/apis/apify-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/apify/apify-api/versions/01a71794279b/schema)