Run a skill and wait
Run a skill and get its rows in the same call.
max_results, max_pages, version, browser_type, profile_id, proxy_config, scrape_mode) sit next to them. See Run settings.
The rows are in data. The other fields are explained in Runs.
If your account already has its maximum of runs in progress, this returns 429 with Retry-After instead of waiting. Use Start a skill run to queue instead.
The older POST /v1/skills/run with skill_id and parameters in the body still works. New code should use this route.
MCP tool: skill_<slug>.Authorizations
API key with the vd_sk_ prefix, as Authorization: Bearer vd_sk_.... Create keys in Settings → API Keys.
Headers
Any unique string (such as your order id). Resending the same request with the same key within 24 hours returns the first answer (with Idempotent-Replayed: true) and does nothing twice; the same key with a different request is a 422 idempotency_key_reused.
1 - 255Path Parameters
Query Parameters
Max rows to return; 0 means the entire list. Omit to use the skill's saved default.
0 <= x <= 500Page limit for paginated skills; 0 means all pages.
x >= 0Recipe version to replay for this call.
x >= 1Body
The skill's inputs at the top level, plus optional run settings: max_pages, version, browser_type, proxy_config, profile_id, scrape_mode.
Response
Skill executed successfully
Response from skill execution.
Why the run came back short, and what a hint could say to fix it (POST /v1/skills/{slug}/improve).

