Integrations & API Tokens

The Integrations page lets workspace administrators manage third-party service integrations and create custom API tokens for authenticating your own tools against the VSEC APIs.

The Integrations page is accessible to users with the Workspace Admin role. Navigate to Account → Workspace → Integrations in the left-hand admin navigation.

AI intelligence providers (Anthropic Claude, Google Gemini, Deep Harbor) are configured on the Intelligence page, not here. The Integrations page covers third-party service integrations and custom API tokens only.

Third-Party Integrations

The upper section of the Integrations page lists the pre-built integrations: VicOne xZETA, VicOne xNEXUS, and Elastiq. Each row shows the integration’s name and enabled state. Integrations that require additional configuration (endpoint URLs, API tokens, etc.) include a Configure button that opens a settings dialog; Configure is disabled until the integration is enabled.

Scan Interval (xZETA SBOM Scanning)

Integrations that run on a recurring schedule — such as xZETA’s automated SBOM scanning — expose an Automated SBOM scan interval (minutes) field in their configuration dialog. This sets how often (in minutes) the integration re-scans, and defaults to 10 minutes.

The interval accepts values from 1 to 1440 minutes. Saving the configuration or toggling the integration reschedules the scan immediately — no restart is required.

Custom API Tokens

The Build your own integration card at the bottom of the page lets you generate long-lived workspace API tokens. Use these tokens to authenticate your own scripts, CI pipelines, or external tools against the VSEC workspace APIs.

Tokens are scoped to the workspace and act with the identity of the user who created them — API calls made with a token carry that user’s permissions in the workspace.

Generating a Token

Click Generate token on the Build your own integration card.
Enter a descriptive Integration name (e.g. My CI Pipeline).
Click Generate token.

Copy the token immediately. It is displayed only once — after you close the dialog the full token cannot be retrieved. If you lose it, generate a replacement and delete the old one.

Use the token as a bearer token in API requests:

Authorization: Bearer <token>

The x-api-key header is accepted as an alternative:

x-api-key: <token>

Managing Tokens

Each token appears in the list with its name and a short token prefix (e.g. abc123…).

Action	Description
Regenerate token	Issues a new token for this integration. The previous token is immediately revoked — update any services using it before regenerating. The new token is not displayed; it is copied to your clipboard and a toast confirms it.
Remove	Opens a Remove integration? confirmation, then permanently revokes the token. Any API requests using this token will stop working immediately. This action cannot be undone.

Last updated on September 18, 2026

Intelligence