Skip to main content
API tokens let other systems, such as a CMDB, BI tool or SIEM, read from M.A.R.C.U.S. through the Public API. Tokens are read-only. You need View API tokens to see the list and Manage API tokens to create or revoke them.

Create a token

  1. Go to API tokens and select New token.
  2. Give it a Name that says what uses it, such as Facilities BI export.
  3. Tick only the Scopes it needs: The other scopes listed (notification channels, reports) are reserved for endpoints not yet in the API.
  4. Choose when it Expires: 30 days, 90 days (the default) or 1 year. Never (not recommended) is also available.
  5. Select Create token, then copy the token.
The token is shown only once. Store it in the integration’s secret store straight away; M.A.R.C.U.S. keeps only a fingerprint of it and can’t show it again.

Keep track of tokens

Tokens start with avb_, and the integration sends one as Authorization: Bearer <token>. The list is split into Active and Revoked tokens. It shows each token’s prefix (such as avb_1a2b3c4d…), how many scopes it has, who created it, when and from where it was last used, and when it expires or was revoked, or no expiry. Expired tokens are marked expired. A token that has never been used, or hasn’t been used for months, may be safe to revoke.

Revoke a token

Select the token’s revoke icon, then Revoke token. The integration using it stops working immediately. The token stays in the list, and its past activity in the audit log, so it can still be traced. A revoked or expired token is deleted 90 days after it was revoked or expired. Active tokens are never deleted. To rotate a token without downtime, create the new one, update the integration, then revoke the old one.
API docs, at the top of the page, opens the interactive API reference for trying calls with a token.

Updated 06 Nov 2026 14:07 · page 56187cd