API Keys

Manage and use your API keys

Manage multiple API keys for different environments and use cases. Each API key can be configured with specific permissions and usage limits.

Creating API Keys

  1. Go to the Console → API Keys
  2. Click Create New Key
  3. Give your key a descriptive name (e.g., "Production Key", "Development Key")
  4. Select the environment: production, staging, or development
  5. Copy and save your key securely
API keys are only shown once upon creation. Store them securely in a password manager or environment variables.

Key Types & Environments

Organize your API keys by environment to keep production data separate from testing:

Production Keys

  • Used for live applications and real user data
  • Starts with ml_live_
  • Full access to all resources and rate limits

Development Keys

  • Used for local development and testing
  • Starts with ml_dev_
  • Isolated from production data
  • More lenient rate limits for testing

Managing Multiple Keys

You can create multiple API keys for different purposes:

  • Primary Key: Your main production key for live applications
  • Backup Key: Secondary production key for rotation
  • Integration Keys: Separate keys for third-party integrations
  • Development Keys: Testing and development environments

Selecting Which Key to Use

When making API requests, you can use any of your active keys. Select the appropriate key based on:

  • Environment: Use production keys for live apps, development keys for testing
  • Integration: Use dedicated keys for each third-party integration
  • Team Member: Create separate keys for each developer or service
# Production requests
curl https://api.missinglettr-api.com/v1/workspaces/ \
  -H "Authorization: Api-Key ml_live_abc123def456..."

# Development requests
curl https://api.missinglettr-api.com/v1/workspaces/ \
  -H "Authorization: Api-Key ml_dev_xyz789ghi012..."

Key Permissions

Each API key has full access to your account resources. For security:

  • Only share keys with trusted team members
  • Use separate keys for each application or integration
  • Revoke keys immediately if compromised

Rotating Keys

Regularly rotate your API keys for security:

  1. Create a new key with the same name + date
  2. Update your application to use the new key
  3. Test that the new key works
  4. Delete the old key from the console
We recommend rotating production keys every 90 days and immediately after any team member leaves.

Monitoring Key Usage

Track which keys are being used and their request volumes:

  • View request counts per key in the console
  • Monitor for unusual activity
  • Set up alerts for rate limit approaches
  • Review last used timestamps

Revoking Keys

Delete compromised or unused keys immediately:

  1. Go to Console → API Keys
  2. Find the key you want to revoke
  3. Click Delete or the trash icon
  4. Confirm deletion
Once deleted, any requests using that key will immediately fail with a 401 Unauthorized error.