SETUP GUIDE

Workspace API keys

Create a named workspace key only when a programmatic integration needs it, then store it in the destination’s secret manager.

Before you start

  • Workspace access
  • A known integration destination such as GitHub Actions, CLI or a server-side deployment secret store

Setup

  1. Open API Keys and choose a specific descriptive name.
  2. Copy the secret when it is shown; it is not displayed again.
  3. Store it only in the destination’s secret store, for example GitHub Actions secrets.
  4. Use the key through the documented API, CLI or integration workflow.

Verify and expected result

The key list shows metadata and active or revoked state, not the secret. Verify the destination with a minimal documented request or workflow run.

A successful integration uses the key without exposing it in source code, logs, tickets or browser-visible configuration.

Common safe checks

The key was exposed or is no longer needed

Revoke it immediately in AntOps, remove it from the destination and create a replacement only if required.

Security and revocation

API-key values are shown once. AntOps support never needs the secret value to diagnose an integration.

Use Revoke in API Keys, then remove the value from every integration that used it.

Open API documentation