Skip to main content

Sender Email and Name

Use the from object to control the sender identity that recipients see in their inbox.
  • from.email (required): The email address. Must use a verified domain in your SendPost account.
  • from.name (optional): The display name shown in email clients.
When both fields are provided, recipients see "Display Name" <email@domain.com>. If only from.email is provided, recipients see the email address only.

Common Use Cases

Support Emails

Recipients see: Support Team <support@example.com>

Marketing Emails

Recipients see: Marketing <marketing@example.com>

Product-Specific Emails

Recipients see: Product Updates <notifications@example.com>

Personal-Style Emails

Recipients see: Sarah from Example <sarah@example.com>

Company Branding

Recipients see: Example Company <hello@example.com>

Examples

Order Confirmation (Transactional)

Newsletter (Promotional)

Password Reset (Security)

Best Practices

  • Use clear, recognizable sender names that match the email type.
  • Maintain consistent sender names across similar email types to build recognition.
  • Avoid generic names like “noreply” which may reduce engagement.
The email address in from.email must belong to a domain verified in your SendPost account. Sending from an unverified domain returns an error.
Webhook payloads include the sender name and email, so you can track which sender identity was used for each email event.