User Menu — API Keys
What it does
Section titled “What it does”The API Keys section lets you view and manage the API key used to integrate MooveTeam CMS with external systems. The key authenticates programmatic access to the MooveTeam CMS API endpoints.
Requirements
Section titled “Requirements”| Requirement | Details |
|---|---|
| Role | Admin or Agency (company-level administrator) |
How to access
Section titled “How to access”User dropdown (top-right) → API Keys
Fields / Options
Section titled “Fields / Options”| Field | Type | Description | Required |
|---|---|---|---|
| Api Key | Display (read-only) | The current API key string (a UUID prefixed with your user ID) | — |
| Creation date | Display (read-only) | Date and time when the current key was generated | — |
| Last used | Display (read-only) | Date and time when the key was last used for an API call | — |
| Times used | Display (read-only) | Total number of API calls made with this key | — |
| Change history | Display (read-only, textarea) | Log of all key regeneration events with timestamps and previous key references | — |
Actions
Section titled “Actions”| Action | Description |
|---|---|
| Regenerate API Key | Generate a new API key, immediately invalidating the previous one |
| Back | Return to the previous screen |
Behavior and rules
Section titled “Behavior and rules”- All fields are read-only — use this page to view key information and regenerate the key, not to edit it.
- A success banner (“Your api key has been regenerated”) confirms the action.
- The change history records every regeneration with the format:
{date} - Api key created - previous key: {old_key}. - There is a notice at the bottom: “You can regenerate API key for security purposes” — regeneration is intended for key rotation or if a key is compromised.
- The “API docs” link is shown below the key field for reference documentation.