Copy page

Projects & Routes

Project API tokens

Project API tokens authenticate the Sending API and SMTP relay. They start with lm_ and are scoped to one project.

Each project can have multiple Project API tokens. Create separate tokens for production, staging, CI, and each integration so you can rotate or revoke one token without interrupting everything else.

Create a token

Manage tokens

The token list shows each token's name, when it was last changed, when it was last used, and the last IP address that used it.

Use the token actions menu to regenerate, revoke, or inspect token logs.

Regenerate or revoke

• Regenerate a token if it may be exposed. The old token stops working immediately.
• Revoke tokens that are no longer used.
• Create a new token before rotating production traffic when you need a zero-downtime credential change.

Best practices

• Use one token per integration or environment.
• Store tokens in a secrets manager or environment variable.
• Never commit tokens to source control or expose them in client-side code.
• Name tokens by owner and purpose, such as billing-service production.
• Review last-used metadata regularly and remove inactive tokens.

Use a Project API token

cURL
curl -X POST "https://api.lettermint.co/v1/send" \
  -H "Content-Type: application/json" \
  -H "x-lettermint-token: $LETTERMINT_PROJECT_TOKEN" \
  -d '{
    "from": "You <you@example.com>",
    "to": ["recipient@example.com"],
    "subject": "Hello",
    "text": "Sent with a Project API token."
  }'

Next steps

• Quickstart - Send your first email
• SMTP guide - Use the same token with SMTP
• Team API tokens - Manage team-level API access