---
title: "Create integration connection"
method: POST
path: "/v1/integrations/connections"
tags: ["Integrations"]
---

# Create integration connection

`POST /v1/integrations/connections`

Create an integration connection so Comp AI can collect evidence, run checks, or sync data from a connected provider.

## Request body

- CreateConnectionDto
  - `organizationId` string — Auto-resolved from your API key / session. You can omit this; it is ignored by the server.
  - `providerSlug` string, required — Provider slug for the integration. Call list-providers first to see the available slugs (e.g. 'aws', 'gcp', 'azure', 'github').
  - `credentials` object — Provider-specific credential fields. Keys differ by provider — call get-provider-details for the exact shape. For AWS (Cloud Tests) the fields are: connectionName (display name), awsType ('aws-commercial' or 'aws-govcloud'), roleArn (auditor role), externalId (typically your org id), regions (string array), and optionally remediationRoleArn and awsScanMode ('comp_scanners' or 'security_hub'). Omit credentials for OAuth providers — use POST /v1/integrations/oauth/start instead.

## Response `201`

## Changes

- **2026-06-04** `d7d0199d846f` — 1 info
  - the endpoint scheme security `oauth2` was removed from the API
- **2026-05-29** `5382c53ab431` — 1 info
  - the endpoint scheme security `oauth2` was added to the API
- **2026-05-28** `73c1d2d2da5d` — 1 info
  - added the new optional request property `organizationId`
- **2026-05-28** `7c0713bef5b1` — 1 breaking
  - added required request body

[Change history](https://skmtc.dev/trycompai/apis/comp-ai-api/changes/v1/integrations/connections/post.md)

---

[API](https://skmtc.dev/trycompai/apis/comp-ai-api.md) · [All operations](https://skmtc.dev/trycompai/apis/comp-ai-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/trycompai/comp-ai-api/revisions/726b9523fb22/schema)