Run an Apify Actor synchronously and get its dataset items back in a single HTTP call

Documented steps

1. POST https://api.apify.com/v2/acts/{actorId}/run-sync-get-dataset-items — actorId is the Actor ID or the 'username~actor-name' form. This runs the Actor and returns its default dataset items in one blocking call.
2. Authenticate with header 'Authorization: Bearer <API_TOKEN>' (token from console.apify.com Integrations page). The docs mark the '?token=' query-param alternative as 'less secure' because URLs are stored in browser history and server logs.
3. Send the Actor input as the JSON request body with 'Content-Type: application/json'; the raw body becomes the run's INPUT record. Use the GET variant of the same path when you need no input.
4. Run-control query params: build (default 'latest'), memory (MB, power of 2, min 128), timeout (seconds), maxItems and maxTotalChargeUsd (cost caps for pay-per-result / pay-per-event Actors), restartOnError, webhooks (base64-encoded JSON array).
5. Output-shaping query params: format (json default, or jsonl/csv/html/xlsx/xml/rss), clean, fields, omit, limit, offset, desc, unwind, flatten, attachment, delimiter, bom, skipHeaderRow, skipHidden, skipEmpty, simplified, view, xmlRoot, xmlRow.
6. On success the endpoint returns HTTP 201 with the dataset items in the requested format, plus pagination headers X-Apify-Pagination-Offset / -Limit / -Count / -Total.
7. If the run exceeds 300 seconds the docs state the HTTP response returns status 408 (Request Timeout) — the run itself continues server-side. For anything longer, use the async run + poll pattern instead.
8. Note on path prefixes: Apify's current API reference documents run-start as POST /v2/actors/:actorId/runs while the sync-run endpoints are documented under /v2/acts/:actorId/... — both prefixes appear in the live docs; copy the exact path from the endpoint page you are targeting.
9. Docs: https://docs.apify.com/api/v2/act-run-sync-get-dataset-items-post