Customer API

Use Administration → API keys to create a dedicated credential for SOAR, SIEM, and internal scripts.

The organization license key is only for TAO / GenGuard enrollment. It is not accepted on the Customer API. If a license leaks, revoke and rotate it separately - API access still requires a portal-issued key with explicit scopes.

Before you begin

• You must be an Owner or Admin.
• Decide which data the integration may read: organization metadata, TAO agents, alerts, and/or audit events.
• Store the secret in your vault. Trustity shows the raw key once.

Create a key

1. Open Administration → API keys.
2. Enter a name (for example siem-prod).
3. Select one or more scopes. Unchecked scopes return HTTP 403.
4. Select Create API key and copy the trst_live_… value immediately.
5. Configure your client with Authorization: Bearer <key> against https://www.trustity.io/api/v1.

What v1 can read

• Organization name, plan, and modules (never the license key)
• TAO agent inventory (status and last seen - no agent secrets)
• VisionX incident summaries and alert outbox (no evidence frames)
• Recent portal audit events

Writes (policy, lock, invites) and GenGuard browser data are not in v1.

Revoke

Revoke unused or leaked keys on the same page. Revocation takes effect immediately. Create a new key if scopes must change.

Reference

The full request contract, curl examples, and error codes live in Developer Central: TCP Customer API.