Start an Apify actor run in the background
apify.web.scrape.job.startStart a scraper run in the background and get back its run id
- Price
- freeプロバイダー原価
- Success rate
- 99.9%Last 30 days · 1,509 calls
- Latency p50
- 4.4 sp95 15 s
- Last verified
- 2026/07/31Verified working
POSThttps://toolswitch.dev/v1/tools/apify.web.scrape.job.start?memory=256&timeout=60&waitForFinish=0&maxTotalChargeUsd=0.05Preview- Uses platform quota
- Synchronous response
- Reads public data
パラメータ
the whole request body IS the actor's input object — there is no wrapper key; use the same fields as the run-sync entries above (startUrls/resultsLimit for the Facebook actor, search/limit for the TikTok one). Returns immediately with {data: {id, status, defaultDatasetId}}. This is the route for anything that outruns run-sync's 300-second ceiling: keep `id` to poll and `defaultDatasetId` to collect results. The test_request deliberately targets apify~hello-world rather than a data actor — REPLAYING IT STARTS A REAL RUN, and hello-world is the cheapest actor that exists (observed 2026-07-31: $0.00013 of compute, no results, so nothing pay-per-result can bill). Verified live 2026-07-31 that /actors/{id}/runs and the older /acts/{id}/runs are the same endpoint — both answer 201
| パラメータ | 型 | 必須 | 説明 | 例 |
|---|---|---|---|---|
| パスパラメータ | ||||
actor_id | 文字列 | 必須 | username~actorname with a TILDE, e.g. apify~facebook-ads-scraper | apify~facebook-ads-scraper |
| クエリパラメータ | ||||
memory | 整数 | 任意 | MB; higher memory is faster and costs more compute | 2048 |
timeout | 整数 | 任意 | seconds the RUN may take (not the HTTP call) | 900 |
maxItems | 整数 | 任意 | result cap for pay-per-result actors | 500 |
waitForFinish | 整数 | 任意 | seconds to hold the HTTP response open waiting for the run, max 60 — a middle ground between async and run-sync | 0 |
maxTotalChargeUsd | 数値 | 任意 | 5 | |
- パスパラメータ
actor_id文字列必須username~actorname with a TILDE, e.g. apify~facebook-ads-scraper
例：
apify~facebook-ads-scraper- クエリパラメータ
memory整数任意MB; higher memory is faster and costs more compute
例：
2048timeout整数任意seconds the RUN may take (not the HTTP call)
例：
900maxItems整数任意result cap for pay-per-result actors
例：
500waitForFinish整数任意seconds to hold the HTTP response open waiting for the run, max 60 — a middle ground between async and run-sync
例：
0maxTotalChargeUsd数値任意例：
5
コード例
$TOOLSWITCH_KEY をコンソールで作成したキーに置き換えてください。
curl -X POST 'https://toolswitch.dev/v1/tools/apify.web.scrape.job.start?memory=256&timeout=60&waitForFinish=0&maxTotalChargeUsd=0.05' \
-H "X-Toolswitch-Key: $TOOLSWITCH_KEY" \
-H "Content-Type: application/json" \
--data-raw '{}'import os
import json
import requests
response = requests.request(
"POST",
"https://toolswitch.dev/v1/tools/apify.web.scrape.job.start?memory=256&timeout=60&waitForFinish=0&maxTotalChargeUsd=0.05",
headers={"X-Toolswitch-Key": os.environ["TOOLSWITCH_KEY"]},
json=json.loads("{}"),
)
response.raise_for_status()
print(response.text)const response = await fetch("https://toolswitch.dev/v1/tools/apify.web.scrape.job.start?memory=256&timeout=60&waitForFinish=0&maxTotalChargeUsd=0.05", {
method: "POST",
headers: {
"X-Toolswitch-Key": process.env.TOOLSWITCH_KEY ?? "",
"Content-Type": "application/json",
},
body: JSON.stringify(JSON.parse("{}")),
});
if (!response.ok) throw new Error(`Request failed: ${response.status}`);
console.log(await response.text());このゲートウェイ API はプレビュー版です。URL や認証方式は変更される場合があります。 パラメータはサンプルデータです。 呼び出し料金は free です。サービス料を含みます。