API tokens

Both CloudVision360 and ITOps360 publish a REST API with scoped tokens, so you can automate reporting, export data or drive the platform from your own systems.

The permission model

A token can only ever carry a subset of its creator’s permissions. You cannot mint a token more powerful than yourself, and a token’s actions are checked against its scope on every request, exactly like a signed-in user. Every call is recorded in the audit trail.

Create a token

1. In CloudVision360, open Admin → Users & access → API tokens (the gear at the bottom of the icon rail) and create a token.
2. Give it a name and choose the permission scopes it needs — grant as few as possible.
3. Optionally set an expiry.
4. Copy the token value now; it is shown once and never again.

Discover the endpoints

Each product publishes a machine-readable catalog of its endpoints and the permission each one requires at /api/catalog in your workspace. Use it to see exactly which scope a call needs.

Call the API

Send the token as a bearer header:

curl -H "Authorization: Bearer $CV360_TOKEN" \
  https://app.cloudvision360.com/api/findings?status=open

Rotate and revoke

Rotate tokens on a schedule and revoke any token immediately from the same page if it may be exposed. Revocation takes effect on the next request.