Token View History

Acefone provides a View History option for API Tokens, allowing customers and support teams to view the audit trail of activities and changes associated with a token after its creation.

The History view provides visibility into what happened, when it happened, how the action was performed, who or what performed the action, and what changed.

Accessing Token History

To view the history of an API Token:

Navigate to API Tokens.
Locate the required API Token.
Open the Action (⋮) menu.
Select View History.
The token's history and audit details are displayed in the History panel.

The View History option is available from the Action menu and is positioned between Edit and Blacklist.

History Events

The History view displays the activities performed on the API Token, including:

Event	Description
Created	Indicates when the API Token was created.
Access Control Updated	Indicates that access control settings associated with the token were modified.
Name Updated	Indicates that the token name was changed.
Blacklisted	Indicates when the token was blacklisted.
Whitelisted	Indicates that the token was removed from the Blacklist and restored to an eligible state.
Renewed → Superseded	Indicates that the token was renewed through the Token Rotation API and the existing token was superseded.

Each history entry provides the following information, wherever applicable:

Event Type – The action performed on the token.
Timestamp – Date and time when the event occurred.
Channel / Source – Indicates whether the action was performed through the Dashboard or an API.
Actor – Identifies the user, system, or API responsible for the action.
Change Details – Displays the relevant change or before-and-after values where applicable.

Channel / Source

The History view identifies the channel through which an event was performed.

Event	Channel / Source
Created	Dashboard / API
Access Control Updated	Dashboard
Name Updated	Dashboard
Blacklisted	Dashboard
Whitelisted	Dashboard
Renewed	API

The channel information is displayed only within the History view and is not added as a column to the main API Token list.

The history design also supports future API-based operations. If APIs are introduced for actions such as Access Control, Blacklist, or Whitelist in the future, those events can be recorded with API as the source.

Token Rotation History

When an API Token generated from the Acefone portal is rotated using the Token Rotation API, the token history reflects the rotation event.

For example:

Existing Token → Token Rotation API → New Token

The history of the existing token records the renewal/rotation event and indicates that the token was Superseded. The newly generated token is created as Active and maintains its own token history.

This allows administrators and support teams to trace the relationship between the previous token and the newly generated token and understand when the rotation occurred and through which channel.

Example

If a portal-generated token is rotated through the API:

Existing Token

Event: Renewed → Superseded
Channel: API
Actor: API/System
Timestamp: Date and time of rotation
Change Details: Token rotated and replaced by a new token

New Token

Event: Created
Channel: API
Actor: API/System
Timestamp: Date and time of token generation
Status: Active

📘
Important: Token History provides an audit trail of token lifecycle and configuration changes. It does not extend the validity of an expired token or allow a non-active token to be rotated.

Understanding Token History

The History panel provides a chronological view of token activity so that customers and support teams can easily determine:

What happened → When → Through which channel → Who/what performed it → What changed

This provides better visibility into token lifecycle events, including token creation, configuration changes, blacklist/whitelist actions, and token rotation.