List durable executions for a GitHub automation binding

GET/v1/github/automations/bindings/{id}/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

Name	Location	Type	Required	Description
id	path	string	Yes	—

Query parameters

Name	Location	Type	Required	Description
limit	query	integer	No	—

Header parameters

Name	Location	Type	Required	Description
X-Computer-Agents-Organization	header	string	No	Active 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.

200Automation executions ordered newest firstapplication/json

Field	Type	Required	Description
object	list	Yes	—
data	object[]	Yes	—
data[].id	string	Yes	Unique identifier.
data[].bindingId	string	Yes	—
data[].organizationId	string	Yes	—
data[].deliveryId	string	Yes	—
data[].eventType	string	Yes	—
data[].action	string	Yes	—
data[].headSha	string	Yes	—
data[].status	queued \| running \| succeeded \| failed \| ignored	Yes	Current lifecycle status.
data[].securityRunId	string	Yes	—
data[].threadId	string	Yes	Thread ID.
data[].error	string	Yes	—
data[].metadata	object	Yes	Free-form metadata object.
data[].createdAt	string	Yes	ISO 8601 timestamp.
data[].updatedAt	string	Yes	ISO 8601 timestamp.
data[].completedAt	string	Yes	ISO 8601 timestamp.
hasMore	boolean	Yes	—

404Resource not foundapplication/json

Field	Type	Required	Description
error	string	No	—

List durable executions for a GitHub automation binding

Response 200

See the ACP quickstart and SDK flow