POST /flows/:id/run
Runs the whole pipeline in node order.
curl -X POST https://api.jetscrape.com/flows/flow_abc123/run \
-H "Content-Type: application/json" \
-H "x-api-key: js_YOUR_API_KEY" \
-d '{
"overrides": {
"node_xyz": { "url": "https://example.com/different-page" }
}
}'overrides(object) — maps a node id to the fields of itsrequest_bodyyou want to replace for this run. The saved flow is not modified.
Overrides let you point the same pipeline at a different target without duplicating the flow.
POST /flows/:id/nodes/:nodeId/run
Runs a single node — the way to test one step in isolation while you are building.
curl -X POST https://api.jetscrape.com/flows/flow_abc123/nodes/node_xyz/run \
-H "Content-Type: application/json" \
-H "x-api-key: js_YOUR_API_KEY" \
-d '{}'Reading the results
The run response carries a dispatch_id. Use it to poll for progress and results.
curl -X POST https://api.jetscrape.com/webhook/check-job \
-H "Content-Type: application/json" \
-H "x-api-key: js_YOUR_API_KEY" \
-d '{ "dispatch_id": "disp_abc123" }'Credits
Each node costs whatever its own scrape costs, so a flow run costs the sum of the nodes that execute. Running a single node charges only for that node.
Debugging order
- Run the node on its own and check whether
datais populated. - If it is empty, revisit the selectors and
wait_until— see Rendering and Waiting. - Once the node is right, run the whole flow.
- If the flow stops midway, look at which step returned
success: falsein thecheck-joboutput.
While iterating, run one node at a time instead of the whole flow. It is faster and costs a fraction of the credits.