Overview
API keys enable programmatic access to the ActumX API. Each key is associated with a user account and can be revoked at any time.List API Keys
Retrieve all API keys for the authenticated user.This endpoint requires session authentication (dashboard login), not API key authentication.
Response
List of API key objects
Create API Key
Generate a new API key for programmatic access.This endpoint requires session authentication (dashboard login).
Request Body
Display name for the API key
- Minimum length: 2 characters
- Maximum length: 80 characters
Response
Unique identifier for the created key
The full API key value
First 14 characters for identification
Security warning about storing the key
Revoke API Key
Revoke an API key to prevent further use. Revoked keys cannot be reactivated.This endpoint requires session authentication (dashboard login).
Path Parameters
The ID of the API key to revoke
Response
Whether the revocation was successful
Revoking a key sets its
revokedAt timestamp. The key becomes immediately unusable for API requests.Key Format and Security
Key Structure
API keys follow this format:actumx_live_x) serve as the prefix for easy identification.
Storage
- Keys are stored as SHA-256 hashes in the database
- Only the hash and prefix are retained after creation
- The full key is only displayed once at creation
Last Usage Tracking
ThelastUsedAt field is updated whenever an API key successfully authenticates a request. This helps you identify unused keys.
Error Codes
| Status | Error | Description |
|---|---|---|
| 401 | unauthorized | Not logged in or session expired |
| 200 | success: true | Revocation succeeded (even if key doesn’t exist) |
Revoking a non-existent or already-revoked key returns success to prevent information disclosure.