List durable source synchronization executions

GET/v1/source-control/bindings/{bindingId}/executions

How to call this endpoint

Every ACP API request uses bearer authentication. The examples here show the actual request path, auth header, and body shape that the platform expects.

Path, query, and header parameters

These parameters control which ACP object the endpoint acts on and how the request is processed.

Path parameters
NameLocationTypeRequiredDescription
bindingIdpathstringYes
Query parameters
NameLocationTypeRequiredDescription
limitqueryintegerNo
Header parameters
NameLocationTypeRequiredDescription
X-Computer-Agents-OrganizationheaderstringNoActive organization context. If omitted, the authenticated user's personal organization is used.

Body schema

This endpoint does not require a request body.

None.

What the API returns

Each response code below includes the documented payload shape for the ACP API.

200Source synchronization executions ordered newest firstapplication/json
FieldTypeRequiredDescription
objectlistYes
dataobject[]Yes
data[].idstringYesUnique identifier.
data[].bindingIdstringYes
data[].organizationIdstringYes
data[].directiongithub_to_resource | resource_to_githubYes
data[].triggerTypestringYes
data[].sourceEventIdstringYes
data[].githubShastringYes
data[].resourceRevisionstringYes
data[].statusqueued | running | succeeded | failed | ignored | conflictedYesCurrent lifecycle status.
data[].attemptCountintegerYes
data[].availableAtstringYes
data[].claimOwnerstringYes
data[].claimExpiresAtstringYes
data[].errorstringYes
data[].metadataobjectYesFree-form metadata object.
data[].createdAtstringYesISO 8601 timestamp.
data[].updatedAtstringYesISO 8601 timestamp.
data[].completedAtstringYesISO 8601 timestamp.
hasMorebooleanYes
404Resource not foundapplication/json
FieldTypeRequiredDescription
errorstringNo
List durable source synchronization executions
Loading...
Response 200
Loading...
See the ACP quickstart and SDK flow