Connect a resource to a GitHub source

POST/v1/source-control/bindings

Creates or replaces the single canonical GitHub binding for the resource. Outbound synchronization requires repository contents write permission, and pull-request publication requires pull requests write permission.

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
None.
Query parameters
None.
Header parameters
NameLocationTypeRequiredDescription
X-Computer-Agents-OrganizationheaderstringNoActive organization context. If omitted, the authenticated user's personal organization is used.

Body schema

Content type: application/json · Required

FieldTypeRequiredDescription
resourceKindfunction | web_app | skill | agent | computerYes
resourceIdstringYes
repositoryFullNamestringYes
baseBranchstringNo
rootPathstringNo
directiongithub_to_resource | resource_to_github | bidirectionalNo
conflictPolicyfail | github_wins | resource_winsNo
enabledbooleanNo
configurationobjectNo
configuration.inboundTriggersmanual | push | pull_request.merged | release.published[]No
configuration.outboundTriggersmanual | resource.updated | resource.published[]No
configuration.branchPrefixstringNo
configuration.createPullRequestsbooleanNo
configuration.forcePushbooleanNo

What the API returns

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

201Source-control binding createdapplication/json
FieldTypeRequiredDescription
idstringYesUnique identifier.
providergithubYes
resourceKindfunction | web_app | skill | agent | computerYes
resourceIdstringYes
organizationIdstringYes
userIdstringYesUser ID.
createdByUserIdstringYes
repositoryFullNamestringYes
repositoryExternalIdstringYes
installationExternalIdstringYes
baseBranchstringYes
rootPathstringYes
directiongithub_to_resource | resource_to_github | bidirectionalYes
conflictPolicyfail | github_wins | resource_winsYes
enabledbooleanYes
configurationobjectYes
configuration.inboundTriggersmanual | push | pull_request.merged | release.published[]No
configuration.outboundTriggersmanual | resource.updated | resource.published[]No
configuration.branchPrefixstringNo
configuration.createPullRequestsbooleanNo
configuration.forcePushbooleanNo
stateobjectYes
state.lastGitHubShastringYes
state.lastImportedShastringYes
state.lastExportedShastringYes
state.lastResourceRevisionstringYes
state.managedPathsstring[]Yes
state.lastSyncAtstringYes
state.lastSyncDirection | github_to_resource | resource_to_githubYes
state.lastStatus | queued | running | succeeded | failed | ignored | conflictedYes
state.lastErrorstringYes
createdAtstringYesISO 8601 timestamp.
updatedAtstringYesISO 8601 timestamp.
404Resource not foundapplication/json
FieldTypeRequiredDescription
errorstringNo
409Repository connection or GitHub App permissions must be updated
None.
Connect a resource to a GitHub source
Loading...
Response 201
Loading...
See the ACP quickstart and SDK flow