Queue a manual source synchronization

POST/v1/source-control/bindings/{bindingId}/sync

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
bindingId	path	string	Yes	—

Query parameters

None.

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

Content type: application/json · Required

Field	Type	Required	Description
direction	github_to_resource \| resource_to_github	Yes	—

What the API returns

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

202Durable synchronization execution queuedapplication/json

Field	Type	Required	Description
id	string	Yes	Unique identifier.
bindingId	string	Yes	—
organizationId	string	Yes	—
direction	github_to_resource \| resource_to_github	Yes	—
triggerType	string	Yes	—
sourceEventId	string	Yes	—
githubSha	string	Yes	—
resourceRevision	string	Yes	—
status	queued \| running \| succeeded \| failed \| ignored \| conflicted	Yes	Current lifecycle status.
attemptCount	integer	Yes	—
availableAt	string	Yes	—
claimOwner	string	Yes	—
claimExpiresAt	string	Yes	—
error	string	Yes	—
metadata	object	Yes	Free-form metadata object.
createdAt	string	Yes	ISO 8601 timestamp.
updatedAt	string	Yes	ISO 8601 timestamp.
completedAt	string	Yes	ISO 8601 timestamp.

404Resource not foundapplication/json

Field	Type	Required	Description
error	string	No	—

409Requested synchronization direction is disabled

None.

Queue a manual source synchronization

Response 202

See the ACP quickstart and SDK flow