Batch submission receipt
GET/api/v1/videos/batch/:batch_id
The submission receipt for a batch created by POST /v1/videos/batch or POST /v1/videos/batch/upload. counts rolls up per-status totals; items lists each row with its individual status/error and the ids it produced (video_id, job_id).
This is not indexing progress. Every item's status is written once, when the item is submitted, and nothing updates it afterwards — submitted means "we accepted it", never "it finished indexing". So this response does not converge on its own: polling it and waiting for completion waits forever (the same caveat as counts.pending, which likewise never drains by itself).
For indexing outcome, follow the per-item ids: GET /v1/videos/{video_id} for the video's status and result, or GET /v1/jobs/{job_id} for the latest attempt's progress and failure reason. Store video_id — job_id is superseded by every re-index.
Request
Responses
- 200
- 401
- 403
- 404
- 422
- 500
Successful Response
Missing or invalid API key. Add Authorization: Bearer vuf_live_<keyid>.<secret>.
Key used outside the public API roots (/api/v1, /api/v1.1).
Referenced resource (video / job / ad) not found.
Request body failed validation.
Upstream service error — usually safe to retry.