List Sume Format runs: cursor pages, newest first, one Format only
Sume lists Format runs per Format, newest first, limit 1 to 100 and a next_cursor. There is no cross-Format list, so keep your own index of run ids.
Sume lists Format runs one Format at a time, newest first, with limit from 1 to 100 (default 20) and a next_cursor that you send back as cursor until has_more is false. There is no cross-Format list: GET /v1/format-runs is not a collection endpoint. If you need every run across Formats, keep your own index keyed by the run id you stored at create. Source: Format runs and results, read 2026-10-06.
What are the paging rules?
The list is a page, not a feed.
| Field | Value |
|---|---|
limit | 1 to 100, default 20 |
| Order | Newest first |
| Next page | Send next_cursor as cursor |
| Last page | has_more is false |
| Foreign cursor | 400 invalid_request |
What should I store?
Store data.id from every create receipt, together with your order id. That gives you the cross-Format view the API does not, and it lets you fetch any receipt from its result_url later.
Sources
Related posts
More in Formats
- Format run output_extraction_failed: it stays completed, read again
output_extraction_failed is a transport failure, not a verdict. The run stays completed and Sume projects the output again on your next read of the receipt.
- Format run failed primary_not_deliverable: audio under a video key
A Format that makes video fails with agent_reported_failure and primary_not_deliverable when the primary output is audio or a still. How to read and fix it.
- Format run scene status stand-in vs failed: which scenes to retry
Give each scene a status of succeeded, stand-in or failed, then retry only the bad ones with previous_run_id. The schema, the receipt rule and the call.
- Sume Format run timeout: your client stops, the run keeps billing
A client timeout on a Sume Format run does not cancel it. The run continues and bills. Store the run id, read expires_at, and call cancel_url to stop it.
Written by Sume