ANTE User Manual

API Tokens

The API Tokens page is where you issue and manage the secret access tokens that let external websites, apps, and systems connect to your CMS content programmatically.

Overview

A token is a secret key that an outside system uses to authenticate with your CMS. Each token has a type that controls what it can do. From this page you can create new tokens, view the tokens that already exist, copy a token's prefix, regenerate a token, or delete one you no longer need.

To open it, go to CMS → API.

Token Types

Every token is one of three types:

TypeLabelWhat it allows
READ_ONLYRead OnlyRead access
FULL_ACCESSFull AccessRead and modify access
CUSTOMCustomA token with a custom-defined scope

Page Layout

The page has a Create Token button in the top-right corner, and two main areas below it.

Main Token Cards

Two cards at the top of the page surface your primary Read Only and Full Access tokens.

  • If the matching primary token has not been set up yet, the card shows Not configured.
  • When a token exists, its card shows:
    • The token name with its type icon
    • An Active or Inactive status badge
    • The token prefix (the visible start of the token, followed by ...)
    • Type, Last used (or Never), and Expires (only if an expiry is set)
    • Copy Prefix and Regenerate buttons

All Tokens Table

Below the cards, the All Tokens section lists every token you have created. If there are none, it shows an empty state reading No tokens created yet.

ColumnDescription
NameThe token name, with its description underneath if one was provided
TypeRead Only, Full Access, or Custom
StatusActive or Inactive
Last UsedWhen the token was last used, or Never
ActionsA Regenerate (refresh) icon and a Delete (trash) icon

Field Reference

The Create Token dialog has these fields:

FieldRequiredNotes
Token NameYesA name for the token, e.g. Frontend App Token. Leaving it blank shows the error Token name is required.
Token TypeNoA dropdown of Read Only, Full Access, or Custom. Defaults to Read Only.
DescriptionNoAn optional note describing what the token is for.

Common Tasks

Creating a Token

  1. Click Create Token (top right).

  2. Fill in the form:

    • Token Name (required)
    • Token Type — choose Read Only, Full Access, or Custom
    • Description (optional)

  3. Click Create.

  4. The new token value is shown once in a confirmation dialog with the message Copy this token now. You won't be able to see it again.

    Copy it immediately

    The full token value is displayed only once. Click Copy to copy it to your clipboard, then Done to close. There is no way to view the full value again afterward.

Copying a Token Prefix

On a token card, click Copy Prefix to copy the visible prefix of the token to your clipboard. A Token copied to clipboard confirmation appears. (This copies only the prefix, not the full secret.)

Regenerating a Token

  1. Click Regenerate on a token card, or the refresh icon in the All Tokens table.
  2. A confirmation dialog warns: Regenerating will invalidate the current token. Any applications using the old token will need to be updated.
  3. Click Regenerate to confirm.
  4. The new token value is displayed once — copy it right away, then click Done.

Deleting a Token

  1. Click the delete (trash) icon for the token in the All Tokens table.
  2. A confirmation dialog warns: Are you sure you want to delete this token? Any applications using it will lose access.
  3. Click Delete to confirm.

Tips

  • Copy tokens immediately — the full value is shown only once, right after it is created or regenerated.
  • Prefer Read Only — give each external system only the access it needs.
  • Regenerate if compromised — if a token may have leaked, regenerate it to invalidate the old value.
  • Check Last Used — the table shows when each token was last used, helping you spot tokens you can safely delete.

💡 Note: Treat API tokens like passwords. Anyone holding a token can access your CMS content according to that token's type.

← Previous
API
Next →
Webhooks