List connector route runs
Changed onLists execution history for one connector route. Use this route-scoped view when a route detail screen or orchestrator needs only runs belonging to the selected route. Tenant-wide operational dashboards should use /runs and its filters.
Request
- Base URLhttps://api.example.com/api/connector/v1
- AuthHTTP bearer
- TypeScriptA function with typed inputs. Its response is checked against the schema.
Path parameters
Stable identifier for a connector route.
Stable identifier of a connector route that composes a source operation, destination operation, optional transformation, and trigger policy.
Query parameters
Execution status of a route run or connector operation run.
Filters connector executions by lifecycle status.
Stable platform identifier for a configured connector instance.
Filters connector executions by the registry connector instance id.
Stable identifier of the domain invocation binding that caused a connector call.
Filters connector executions by Phase 5 invocation binding lineage.
Stable identifier of a tenant, OU, brand, legal-entity, or channel usage binding for a physical connector instance.
Filters connector executions by logical connection binding lineage.
Stable platform identifier for a configured connector instance.
Filters connector executions by physical connector instance lineage.
Explicit exchange quadrant. Data direction and initiation side remain separate axes in run responses.
Filters connector executions by the Phase 5 data-direction and initiation-side quadrant.
Product, protocol, form, portal, workflow, or application surface that owns a connector invocation binding.
Filters connector executions by the product, protocol, form, portal, workflow, or application surface that initiated the run.
Filters connector executions by durable route-run correlation id.
Zero-based page index.
Page size.
Response
Paged connector runs for the route.
Example response
{
"data": [
{
"runId": "9a785884-63ea-4b07-9976-264a1fc595f1",
"routeId": "1e8ff011-2274-4f16-a7dd-bf0b4fd5262f",
"status": "PARTIALLY_FAILED",
"startedAt": "2026-06-18T10:20:00Z",
"finishedAt": "2026-06-18T10:21:12Z",
"itemCount": 250,
"successCount": 247,
"failureCount": 3
}
],
"pagination": {
"limit": 20,
"offset": 0,
"page": 0,
"size": 20,
"total": 1,
"totalPages": 1,
"hasMore": false
}
}Changes
- breaking
removed the enum value
EXTERNALLY_INITIATED_READ_FROM_VDXfrom thequeryrequest parameterexchangeMode - breaking
removed the enum value
EXTERNALLY_INITIATED_WRITE_INTO_VDXfrom thequeryrequest parameterexchangeMode - warning
added the new
EXTERNALLY_INITIATED_READenum value to the//response property for the response status - warning
added the new
EXTERNALLY_INITIATED_WRITEenum value to the//response property for the response status - warning
added the new
INBOUNDenum value to the//response property for the response status - warning
added the new
OUTBOUNDenum value to the//response property for the response status - info
added the new enum value
EXTERNALLY_INITIATED_READto thequeryrequest parameterexchangeMode - info
added the new enum value
EXTERNALLY_INITIATED_WRITEto thequeryrequest parameterexchangeMode - info
removed the
EXTERNALLY_INITIATED_READ_FROM_VDXenum value from the//response property for the response status - info
removed the
EXTERNALLY_INITIATED_WRITE_INTO_VDXenum value from the//response property for the response status - info
removed the
INTO_VDXenum value from the//response property for the response status - info
removed the
OUT_OF_VDXenum value from the//response property for the response status - info
the
////response's property pattern^sha256:[0-9a-f]{64}$was added for the status - info
the
////response's property pattern^sha256:[0-9a-f]{64}$was added for the status - info
the
////response's property pattern^sha256:[0-9a-f]{64}$was added for the status - info
the
////response's property pattern^sha256:[0-9a-f]{64}$was added for the status
- breaking