# How do I create a sender / from address?

> You do not pre-create senders in SendPing — any address on a verified domain works as a from. Use the Name <you@domain.com> format.

There is **no separate "sender" object** to create in SendPing. Unlike platforms that make you register and verify each individual from address, SendPing verifies at the **domain** level. Once a domain is verified, **any address on it** can be used as the `from` of an email or campaign — no extra setup per address.

## How it works

1. **Verify your domain once** — Add your domain under Domains and publish its SPF/DKIM/DMARC records. See [Managing domains](https://www.sendping.co/docs/domains/managing).
2. **Pick any address on it** — After the domain is verified, `hello@`, `receipts@`, `news@`, `support@`, or any other mailbox on that domain is a valid `from`. You do not create them anywhere first.
3. **Send** — Put the address in the `from` field. SendPing checks the domain part is one of your verified domains and sends.

## The from format

The `from` field accepts either a bare address or a friendly **display name** with the address in angle brackets:

```text
Acme <hello@yourdomain.com>   ← display name + address (recommended)
hello@yourdomain.com          ← bare address
```

SendPing extracts the address from inside the `<…>` and checks that its **domain** (`yourdomain.com`) is verified for your account. A subdomain of a verified domain also works.

**Node.js**

```js
import { SendPing } from 'sendping';

const mb = new SendPing('mb_xxxxxxxxx');

const { data, error } = await mb.emails.send({
  "from": "Acme Support <support@yourdomain.com>",
  "to": ["customer@example.com"],
  "subject": "We got your message",
  "html": "<p>Our team will reply shortly.</p>"
});
console.log({ data, error });
```

**Ruby**

```ruby
require "sendping"

SendPing.api_key = "mb_xxxxxxxxx"

SendPing::Emails.send({
  "from": "Acme Support <support@yourdomain.com>",
  "to": [
    "customer@example.com"
  ],
  "subject": "We got your message",
  "html": "<p>Our team will reply shortly.</p>"
})
```

**PHP**

```php
<?php
require 'vendor/autoload.php';

use SendPing\SendPing;

$sendping = SendPing::client('mb_xxxxxxxxx');

$sendping->emails->send([
  'from' => "Acme Support <support@yourdomain.com>",
  'to' => [
    "customer@example.com"
  ],
  'subject' => "We got your message",
  'html' => "<p>Our team will reply shortly.</p>"
]);
```

**Python**

```python
import sendping

sendping.api_key = "mb_xxxxxxxxx"

sendping.Emails.send({
  "from": "Acme Support <support@yourdomain.com>",
  "to": [
    "customer@example.com"
  ],
  "subject": "We got your message",
  "html": "<p>Our team will reply shortly.</p>"
})
```

**Go**

```go
import "github.com/shekhu10/sendping-sdks/sendping-go"

client := sendping.NewClient("mb_xxxxxxxxx")

sent, err := client.Emails.Send(&sendping.SendEmailRequest{
    From:    "Acme Support <support@yourdomain.com>",
    To:      []string{"customer@example.com"},
    Subject: "We got your message",
    Html:    "<p>Our team will reply shortly.</p>",
})
```

**Rust**

```rust
use sendping::{SendEmailOptions, SendPing};

let mb = SendPing::new("mb_xxxxxxxxx");

let params = SendEmailOptions::new(
    "Acme Support <support@yourdomain.com>",
    ["customer@example.com"],
    "We got your message",
)
.with_html("<p>Our team will reply shortly.</p>");
let _sent = mb.emails.send(params).await?;
```

**Java**

```java
import co.sendping.SendPing;
import co.sendping.SendPingResponse;
import co.sendping.requests.SendEmailRequest;

SendPing sendping = new SendPing("mb_xxxxxxxxx");

SendEmailRequest request = SendEmailRequest.builder()
        .from("Acme Support <support@yourdomain.com>")
        .to("customer@example.com")
        .subject("We got your message")
        .html("<p>Our team will reply shortly.</p>")
        .build();

SendPingResponse response = sendping.emails().send(request);
```

**.NET**

```csharp
using SendPing;

ISendPing sendping = SendPingClient.Create("mb_xxxxxxxxx");

var resp = await sendping.EmailSendAsync(new EmailMessage
{
    From = "Acme Support <support@yourdomain.com>",
    To = "customer@example.com",
    Subject = "We got your message",
    HtmlBody = "<p>Our team will reply shortly.</p>",
});
```

**cURL**

```bash
curl -X POST 'https://www.sendping.co/api/emails' \
  -H 'Authorization: Bearer mb_xxxxxxxxx' \
  -H 'Content-Type: application/json' \
  -d '{
  "from": "Acme Support <support@yourdomain.com>",
  "to": ["customer@example.com"],
  "subject": "We got your message",
  "html": "<p>Our team will reply shortly.</p>"
}'
```

**CLI**

```bash
sendping emails send \
  --from 'Acme Support <support@yourdomain.com>' \
  --to 'customer@example.com' \
  --subject 'We got your message' \
  --html '<p>Our team will reply shortly.</p>'
```

> **Warning:** If the `from` domain is not verified you get a `validation_error`: "The domain (…) is not verified." Finish [domain verification](https://www.sendping.co/docs/domains/managing) before sending — there is nothing to create on the sender side.

> **Note:** The `from` address does **not** need to be a real, provisioned mailbox in another system — SendPing only checks that its domain is verified. That said, we recommend using an address that can actually **receive replies** (or setting `reply_to`) so recipients aren’t writing into a void.

> **Note:** Want replies to go somewhere other than the `from`? Set `reply_to` (a `Reply-To` header). The `from` still controls which verified domain the mail is sent from.