API key management (web app)
Use the service API Keys page to create, deactivate, or revoke server credentials. To authenticate a request or SDK client, see Use API keys.
The web app creates API keys with a name only. This interface does not include scope selection, permission levels, or expiration settings.
Layout
The Active Keys list displays each key and its status. To create the first key for a service, click Create Key.
Create a key
- Click Create Key.
- In Name, enter a value such as
Production API Key. - Copy the full secret from the API Key Created dialog before you close it. Apso does not display the full secret again.
Keys are apso_-prefixed secret strings.
The full key is revealed only at creation. After that the list shows a masked value (apso_ prefix plus a few characters, with the rest hidden). Store it in a secret manager immediately because it cannot be retrieved in full later.
View keys
Each key in the Active Keys list shows:
- Name
- Status badge (
Active) - Masked secret with a show/hide toggle (eye icon) and a copy button
- A ⋮ actions menu
Key actions
| Action | Effect |
|---|---|
| Show / hide | Toggles the masked secret display (masked value only; the full secret is not re-revealed) |
| Copy | Copies the key value to the clipboard |
| Deactivate | Sets the key’s status to Deactivated (reversible state change, keeps the record) |
| Revoke | Permanently revokes the key (destructive) |
Key statuses are Active and Deactivated; Revoke removes the key. There is no separate “delete” distinct from revoke, and no “view full key” after creation.
Key limitations
The web app API keys view does not include:
- Access scopes and permission levels (read / write / admin). Creation is name-only.
- Usage tracking. Call counts, rate limits, usage graphs, alerts, reports, and billing implications are not shown on this page.
- Expiration. No expiry can be set in the app.
Related
- API Keys: using keys in requests and SDKs
- Service Settings