Create or update an external group mapping
POST
/v1/identity-connections/{connectionId}/group-mappingsHow 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 |
|---|---|---|---|---|
| connectionId | path | string | Yes | Organization identity connection ID |
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 |
|---|---|---|---|
| externalGroupId | string | Yes | — |
| externalGroupName | string | No | — |
| teamId | string | No | — |
| organizationRole | viewer | member | developer | No | — |
What the API returns
Each response code below includes the documented payload shape for the ACP API.
201External group mappingapplication/json
| Field | Type | Required | Description |
|---|---|---|---|
| data | object | Yes | — |
| data.externalGroupId | string | Yes | — |
| data.externalGroupName | string | No | — |
| data.teamId | string | No | — |
| data.organizationRole | viewer | member | developer | No | — |
| data.id | string | Yes | Unique identifier. |
| data.organizationId | string | Yes | — |
| data.connectionId | string | Yes | — |
| data.createdAt | string | Yes | ISO 8601 timestamp. |
| data.updatedAt | string | Yes | ISO 8601 timestamp. |
Create or update an external group mapping
Loading...
Response 201
Loading...