Skip to main content

Overview

Lettermint organizes your email infrastructure using Projects and Routes. Projects contain your API credentials and house multiple routes that define how emails are processed.

Projects

Projects are API endpoints that authenticate your email sending. Each project has:
  • Unique API Token: A secure token (format: lm_xxx...) used to authenticate API requests
  • Multiple Routes: Different configurations for transactional, broadcast, or inbound emails
  • Team Access Control: Control which team members can access specific projects
  • Domain Associations: Link verified sending domains to your project
  • Message Statistics: Track delivery metrics and performance

API Tokens

Every project has a unique API token that authenticates your requests to Lettermint’s API.
Keep your API tokens secure. Never commit them to version control or expose them in client-side code.
To find your API token:
  1. Navigate to Projects in your dashboard
  2. Select your project
  3. Go to the API Token section
  4. Copy your token (starts with lm_)

Project Hierarchy

Team (Organization)
└── Project 1
    ├── API Token: lm_abc123...
    ├── Route: Transactional
    ├── Route: Newsletter (Broadcast)
    └── Route: Support Inbox (Inbound)
└── Project 2
    ├── API Token: lm_def456...
    └── Routes...

Routes

Routes define how emails are processed within a project. Lettermint supports three route types:

Transactional

Password resets, order confirmations, notifications

Broadcast

Newsletters, announcements, marketing campaigns

Inbound

Receive and process incoming emails via webhooks
Each route type has specific features tailored to its use case. Routes can have their own:
  • Webhooks: Receive delivery events and notifications
  • Suppression Lists: Manage bounced or unsubscribed recipients
  • Settings: Configure route-specific behavior

Team Access Control

Control which team members can access specific projects:
  • Team Owners: Automatically have access to all projects
  • Team Members: Can be granted access to specific projects
  • No Restrictions: If no access restrictions are set, all team members can access the project

Next Steps