Senders

The addresses your emails come from

A sender is a From address on one of your domains: name, address and Reply-To. Each one has its own reputation, so you can see exactly which emails land well.

  • JSON commands
  • Per-sender reputation
  • Your domains or shared ones
  • Impersonation checks
POSThttps://g.sendcorex.com/v1/sendersender:*

How it works

On a verified domain

Senders live on domains you validated, or on a shared domain we already verified. Nothing to publish for the sender itself.

Reputation per address

Delivered, bounced and spam are counted per sender, with a 0–100 score. Split receipts and newsletters to keep problems apart.

Protected from impersonation

Names and addresses that pretend to be banks or big brands are refused, which keeps the whole platform trusted by mailbox providers.

Get started

Only the key is needed before your first request.

  1. 1

    Create an API key with sender scopes

    In the dashboard, open Developers → API Keys and give the key the sender scopes it needs: sender:read, sender:create, sender:update, sender:delete.

    The webmail token does not work here. This API uses the dashboard API key.

  2. 2

    Have a domain ready

    Validate your own domain with the Domains API, or pick one from List Free Domains to start now.

  3. 3

    Create the sender

    Create Sender returns the sender_id. Send from its address with the Email API or SMTP.

The sender

Every command returns senders in this shape.

{
  "sender_id": "K7Q2M9XR4TB8WD1ZC6NF3HJP",
  "email": "hello@acme.com",
  "username": "hello",
  "domain": "acme.com",
  "from_name": "Acme",
  "reply_to": "support@acme.com",
  "description": "Product updates",
  "avatar_color": "#2F6FDB",
  "warmup_enabled": false,
  "reputation": {
    "delivered": 18420,
    "bounced": 131,
    "spam": 6,
    "received_messages": 2210,
    "total_emails": 18557,
    "has_minimum_volume": true,
    "delivery_rate": 99,
    "bounce_rate": 1,
    "spam_rate": 0,
    "engagement_rate": 12,
    "score": 100,
    "status": "Excellent"
  },
  "created_at": "2026-09-02T14:40:12.530Z",
  "updated_at": "2026-10-20T08:15:33.004Z"
}
sender_id

The id you use in every other command.

from_name / email

What recipients see: "Acme" <hello@acme.com>.

reply_to

Where replies go. Use an address someone reads.

reputation

Totals since the sender was created, the rates and a 0–100 score with a status.

Your first request

Create a sender for your newsletter on a validated domain. Replace SENDCOREX_API_KEY with your API key.

curl -X POST 'https://g.sendcorex.com/v1/sender' \
  -H "Authorization: $SENDCOREX_API_KEY" \
  -H 'Content-Type: application/json' \
  -d '{
  "commands": [
    { "command": "create_sender", "args": { "username": "news", "from_name": "Acme News", "reply_to": "news@acme.com", "domain": "acme.com" } }
  ]
}'

You get the sender back with its sender_id. Start sending from news@acme.com right away. The same request in 8 languages is in Create Sender.

Common tasks

One sender per kind of email

receipts@, news@, support@: separate reputations, so a newsletter problem never hits your receipts.

Choosing a good sender

Watch your reputation

Read the score of each sender every day and alert when one drops below Good.

Reading the reputation

Rebrand without losing history

Change the From name or the Reply-To of a sender and keep its reputation.

Update Sender

Start before your domain is ready

Create a sender on a shared domain today and move to yours later.

List Free Domains

Full reference

Everything marked CMD is a command sent through POST /v1/sender, up to 20 per request.