Britive platform release 2026.09.02 is now live in production.

Generate a new token for an existing CSPM integration

Prev Next
Post
/api/cspm/integrations/{name}/rotate

Generates a fresh cleartext token for an existing integration and replaces the stored one, in place -- the integration's id, name, app, description, and ingest URL are all unchanged, so nothing needs reconfiguring on the CSPM tool's side except the token itself. The old token stops working immediately; the new cleartext token is returned once and never stored. createdOn in the response reflects this new token's creation time (it tracks the active token, not the integration record), so admins can tell when a token was last rotated.

Security
HTTP
Type bearer
Path parameters
name
stringRequired

Either the unique, tenant-wide name of the existing integration to rotate, or its generated id ("cspm-") -- same dual lookup as GET (id tried first, falls back to a name match).

Responses
200

Token rotated successfully

object

Response returned on integration creation or token rotation -- token is shown only once

app
string

CSPM application type

name
string

Unique, tenant-wide name given to this integration at creation

description
string

Description of this integration

token
string

Cleartext token -- store securely, will not be shown again

ingestUrl
string

URL to which CSPM events should be sent (/-ingest/)

createdOn
string

Timestamp when the active token was created. Updated on each rotation -- it tracks the token, not the integration record -- so this reflects when the token was last rotated, not necessarily when the integration itself was first created.

actionTemplate
string

The app's outbound webhook payload/action template, to be pasted as-is into the CSPM tool's own webhook/action configuration. Identical for every integration of a given app type. Absent if the app has no such template.

404

No integration found with the given name or id