List Executions
Execution
List Executions
POST
List Executions
Use this API to fetch a paginated page of execution documents for the workspace, always ordered by
Errors:
startedAt descending (newest first). Designed for Console / Portal listing pages.
Get Execution remains the only way to fetch a single execution’s per-URL results subcollection — list never includes results. Each row is identical to the execution object from Get Execution (without includeResults), passed through metadata-stripping.
Endpoint
POST https://api.velt.dev/v2/agents/execution/list
Headers
Your API key.
Your Auth Token.
Body
Filter combinations (whitelist). Exactly one of these three shapes is accepted. Every other combination — including
{}, { organizationId } alone, { documentId } alone, { agentId, organizationId } (no docId), and { agentId, documentId } (no orgId) — is rejected with INVALID_ARGUMENT.{ agentId }— all executions of a single agent across the workspace.{ organizationId, documentId }— all executions on a single document (any agent).{ agentId, organizationId, documentId }— executions of a single agent on a single document.
Params
Example Requests
1. Org + doc, first page (combo #2)
2. Next page via cursor
3. Agent only (combo #1)
4. All three (combo #3)
Response
Success Response
| Field | Type | Description |
|---|---|---|
data.executions | object[] | Page of execution documents (same shape as Get Execution, without results). |
data.nextPageToken | string | Opaque cursor for the next page. Omitted entirely (key absent) when the result set is fully consumed. |
Failure Response
INVALID_ARGUMENT— filter combo violates the 3-shape whitelist;pageSizeout of range;pageTokenempty/malformed/undecryptable; orpageTokenreferences a now-deleted execution.NOT_FOUND— workspace store database could not be resolved.

