Skip to content
FuseScopeFuseScopeFuseScope

Service accounts and API keys

Use this page when a script, CI job or other tool needs to call the FuseScope API.

Automation calls the FuseScope API with an API key. Keys belong to a service account, a non-human identity with its own roles. Creating and managing service accounts needs the Admin role.

Create a service account and key

Section titled “Create a service account and key”
  1. Go to Settings → Service Accounts and click New Service Account.
  2. Enter a Name and click Create Service Account. Names use lowercase letters, digits and hyphens, start with a letter and have at most 50 characters.
  3. In Service Account Details → Overview, pick the Roles and click Save Changes. The roles decide what the keys can do; see roles.
  4. In the Keys tab, click Add Key, enter a name (same rules, up to 80 characters), choose No Expiration or Set Expiration Date and click Create Key.
  5. Copy the key. It is shown only once.

The keys list shows each key’s expiry and when it was last used (Last Observed At). Revoke Key invalidates a key immediately. Deleting the service account removes all its keys.

Call the API

Section titled “Call the API”

Send the key in the SIGNOZ-API-KEY header. Header names are case-insensitive, so SigNoz-Api-Key works too.

Terminal window
curl -H "SIGNOZ-API-KEY: <key>" https://fusescope.example.com/api/v1/service_accounts/me

A request with an expired key is rejected. When a request also carries an Authorization header, the session token in it takes precedence over the key.