List connected Security GitHub repository providers

GET/v1/github/security/installations

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

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.

200GitHub installationsapplication/json
FieldTypeRequiredDescription
objectlistNo
dataobject[]No
data[].idstringNoUnique identifier.
data[].githubInstallationIdstringNo
data[].accountIdstringNo
data[].accountLoginstringNo
data[].accountTypestringNo
data[].targetTypestringNo
data[].repositorySelectionstringNo
data[].permissionsobjectNo
data[].eventsstring[]No
data[].statusactive | suspended | uninstalledNoCurrent lifecycle status.
data[].suspendedAtstringNo
data[].repositoryCountintegerNo
data[].createdAtstringNoISO 8601 timestamp.
data[].updatedAtstringNoISO 8601 timestamp.
has_morebooleanNo
total_countintegerNo
List connected Security GitHub repository providers
Loading...
Response 200
Loading...
See the ACP quickstart and SDK flow