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
- 价格
- free按供应商原价
- 成功率
- 99.9%近 30 天 · 1,509 次
- 延迟 p50
- 4.4 秒p95 15 秒
- 最后验证
- 2026年7月31日实测可用
POSThttps://toolswitch.dev/v1/tools/apify.web.scrape.job.start?memory=256&timeout=60&waitForFinish=0&maxTotalChargeUsd=0.05预览- 可用平台额度调用
- 同步返回
- 读取公开数据
参数
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());网关接口为预览版，地址与鉴权方式可能调整。 示例参数仅为样例数据。 调用按 free 计费，已含服务费。