Skip to main content

Token types

Strix has two types of API tokens:

Personal tokens

  • Attached to one user
  • Expire after 90 days (default)
  • Best for individual scripts and local tools

Service keys

  • Org-level, not attached to a user
  • Can stay valid for a long time (no default expiry)
  • Best for CI/CD pipelines and production integrations
  • Only org admins can create service keys

Default scopes

Service keys default scopes:
Personal tokens default scopes:
webhooks:write and tokens:write are admin-only scopes. You must add them when you create a token. You can change the scopes when you create a token.

Available scopes

Each endpoint specifies the scope that it requires. A token can only call the endpoints that match its scopes.

Using tokens

Include the token in the Authorization header:

Best practices

  • Give each integration only the scopes that it needs (least privilege)
  • Rotate tokens regularly, especially service keys
  • If a token is compromised, revoke it immediately. A revoked token stops operation on the next request
  • Use personal tokens for development and service keys for production