Refresh repositories from GitHub

POST/v1/github/security/installations/{installationId}/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
NameLocationTypeRequiredDescription
installationIdpathstringYesInternal Security GitHub App installation ID
Query parameters
None.
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.

200Refreshed GitHub repositoriesapplication/json
FieldTypeRequiredDescription
objectlistNo
dataobject[]No
data[].idstringNoUnique identifier.
data[].installationIdstringNo
data[].githubRepositoryIdstringNo
data[].nodeIdstringNo
data[].fullNamestringNo
data[].ownerLoginstringNo
data[].namestringNoHuman-readable name.
data[].defaultBranchstringNo
data[].privatebooleanNo
data[].archivedbooleanNo
data[].disabledbooleanNo
data[].monitoredbooleanNo
data[].securityRepositoryIdstringNo
data[].syncedAtstringNo
data[].updatedAtstringNoISO 8601 timestamp.
has_morebooleanNo
total_countintegerNo
Refresh repositories from GitHub
Loading...
Response 200
Loading...
See the ACP quickstart and SDK flow