> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sendpost.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Managing Senders

> Set the sender name and email address that appears in recipient inboxes using the from field.

```json theme={null}
{
  "from": {
    "email": "support@example.com",
    "name": "Support Team"
  },
  "to": [
    {
      "email": "customer@example.com",
      "name": "John Doe"
    }
  ],
  "subject": "Welcome to Our Service!",
  "htmlBody": "<p>Hi John,</p><p>Welcome aboard!</p>",
  "textBody": "Hi John,\n\nWelcome aboard!",
  "trackOpens": true,
  "trackClicks": true
}
```

## 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

```json theme={null}
{
  "from": {
    "email": "support@example.com",
    "name": "Support Team"
  }
}
```

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

### Marketing Emails

```json theme={null}
{
  "from": {
    "email": "marketing@example.com",
    "name": "Marketing"
  }
}
```

Recipients see: `Marketing <marketing@example.com>`

### Product-Specific Emails

```json theme={null}
{
  "from": {
    "email": "notifications@example.com",
    "name": "Product Updates"
  }
}
```

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

### Personal-Style Emails

```json theme={null}
{
  "from": {
    "email": "sarah@example.com",
    "name": "Sarah from Example"
  }
}
```

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

### Company Branding

```json theme={null}
{
  "from": {
    "email": "hello@example.com",
    "name": "Example Company"
  }
}
```

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

## Examples

### Order Confirmation (Transactional)

```json theme={null}
{
  "from": {
    "email": "orders@example.com",
    "name": "Order Confirmation"
  },
  "subject": "Your order has been confirmed"
}
```

### Newsletter (Promotional)

```json theme={null}
{
  "from": {
    "email": "newsletter@example.com",
    "name": "Example Newsletter"
  },
  "subject": "Monthly Newsletter - July 2024"
}
```

### Password Reset (Security)

```json theme={null}
{
  "from": {
    "email": "security@example.com",
    "name": "Security Team"
  },
  "subject": "Password Reset Request"
}
```

## 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.

<Warning>
  The email address in `from.email` must belong to a domain verified in your SendPost account. Sending from an unverified domain returns an error.
</Warning>

<Info>
  Webhook payloads include the sender name and email, so you can track which sender identity was used for each email event.
</Info>