Skip to content

API Keys — Generate & Manage Access Tokens

API Keys let you interact with CloakMetric programmatically. Create keys with specific permissions and expiration dates to integrate CloakMetric into your workflows. Available on Business and Enterprise plans.

  1. Go to Settings > API Keys.
  2. Click Create API Key.
  3. Enter a descriptive name (e.g., “CI/CD Pipeline”, “Internal Tool”).
  4. Select a permission level.
  5. Choose an expiration period.
  6. Click Create.
LevelReadCreate/UpdateDelete
Read-onlyYesNoNo
StandardYesYes (aliases, campaigns)No
Full AccessYesYes (all resources)Yes

Can query aliases, campaigns, email logs, and analytics. Cannot make any changes.

Can create and update aliases and campaigns. Cannot delete resources or access sensitive settings.

Complete access to all API endpoints, including deleting aliases, managing domains, and workspace settings.

OptionDuration
No expirationKey never expires
30 daysExpires after 30 days
90 daysExpires after 90 days
180 daysExpires after 180 days
1 yearExpires after 365 days

Expired keys are automatically disabled. You can create a new key at any time.

All API keys are rate-limited to 1,000 requests per hour by default. If you exceed this limit, requests will return a 429 Too Many Requests response.

Enterprise customers can request custom rate limits through their account manager.

The API Keys page shows all your keys with:

  • Name — Descriptive label you set
  • Permission level — Read-only, Standard, or Full Access
  • Created date
  • Last used — When the key was last used
  • Total calls — Number of API calls made with this key
  • Status — Active or Revoked

Revoke a key to disable it without deleting it. Revoked keys can be referenced for audit purposes but cannot make API calls.

  1. Find the key in the list.
  2. Click Revoke.
  3. Confirm.

Permanently remove a key and its usage history.

  1. Find the key in the list.
  2. Click Delete.
  3. Confirm.
  • Use the minimum permission level needed. Don’t create Full Access keys if Standard will do.
  • Set expiration dates. Rotate keys regularly.
  • Never commit keys to source control. Use environment variables or secret managers.
  • Revoke compromised keys immediately. If a key is exposed, revoke it and create a replacement.