Skip to main content
Every email needs a sender and at least one recipient, but transactional emails often involve more complex addressing — copying a manager on an order confirmation, blind-copying a compliance archive, or routing replies to a support team instead of a no-reply address. Lettr gives you full control over To, CC, BCC, Reply-To, and sender display names.

To Recipients

Send to one or multiple recipients:

CC Recipients

CC recipients receive a copy of the email and are visible to all other recipients. Use CC when transparency matters — for example, copying a manager on a project update or keeping a team lead informed about client communications.

BCC Recipients

BCC recipients receive a copy of the email but are hidden from all other recipients. Common uses include compliance archiving (sending a copy to a records system), internal monitoring (copying a sales pipeline tool), or sending to multiple customers who shouldn’t see each other’s addresses.

Reply-To Address

Reply-To lets you send from one address (like noreply@example.com) while directing replies to another (like support@example.com). This is useful when your sending address is automated but you want replies to reach a real team.

Sender Name

The from_name parameter sets the display name that appears alongside the sender’s email address in the recipient’s inbox. A clear, recognizable sender name improves open rates because recipients can identify who the email is from before reading the subject line:
The recipient will see: Acme Inc <notifications@example.com>

Recipient Limits

Sending to more than 50 recipients requires multiple API calls. For bulk sending, see Batch Sending.

Email Address Validation

Lettr validates all email addresses before accepting a send request. Each address must pass three checks:
  • RFC 5322 format — The address must conform to standard email format
  • Valid DNS records — The domain must have DNS records that accept email
  • Not suppressed — The address must not appear on your account’s suppression list
If any address fails validation, the API rejects the request and the email is not sent to any recipient:

Combined Example

Here’s a realistic example that uses multiple recipient features together — an order confirmation sent to the customer, CC’d to their account manager, BCC’d to the order archive, with replies directed to the support team:

Recipient Parameters Reference