Rotate the organization SCIM bearer token
POST
/v1/identity-connections/{connectionId}/scim-tokenReturns the new plaintext token once. Only its hash is retained.
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
| 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
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.
201One-time SCIM bearer tokenapplication/json
| Field | Type | Required | Description |
|---|---|---|---|
| data | object | Yes | — |
| data.token | string | Yes | — |
| warning | string | Yes | — |
Rotate the organization SCIM bearer token
Loading...
Response 201
Loading...