Documentation Index
Fetch the complete documentation index at: https://docs.runflow.io/llms.txt
Use this file to discover all available pages before exploring further.
What you’ll do
Process a folder of product shots through one model in a single call. One callback fires when every item is done.Prerequisites
- A Runflow API key. Create one.
- The model you want to run. Pick one from
/models. - A list of input URLs or asset IDs.
Steps
Create the batch
POST /v1/models/{model_id}/batches with an array of items, where {model_id} is the slash-delimited provider/model path shown on the model page. Each item is a separate run.Poll or wait
Either poll
GET /v1/batches/{id} or wait for the callback. Batch records expose status_code; terminal callback payloads expose the same value as status. Batches can also finish as partial_succeeded.Read items
GET /v1/batches/{id}/items returns one entry per input with the resolved run_id, status_code, and outputs.Verify it worked
items_failed: 0? You’re done.Troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
| Some items fail, others succeed | Per-input validation error | Read each failed item’s failure_message. |
| Whole batch fails fast | Auth or quota | Check the balance. |
| Callback never arrives | URL not reachable | See Callbacks: local development. |
Related
Runs
Single-input lifecycle.
Callbacks
Async result delivery.