Skip to main content
POST
/
sender
Create sender
curl --request POST \
  --url https://api.sendx.io/api/v1/rest/sender \
  --header 'Content-Type: application/json' \
  --header 'X-Team-ApiKey: <api-key>' \
  --data '{
  "name": "John Smith",
  "email": "john@example.com"
}'
{
  "name": "John Smith",
  "email": "john@example.com"
}
🎯 Key Features:
  • Add new sender addresses
  • Verify domain ownership before adding senders
  • Configure sender names
📋 Verification Process for domain ownership:
  1. Create sender with name and email
  2. Verification email sent automatically
  3. Click verification link in email
  4. Sender marked as verified and ready to use
🔒 Domain Authentication: For better deliverability, authenticate your domain:
  • Add SPF records
  • Configure DKIM signing
  • Set up DMARC policy
  • Complete domain verification in SendX settings
💡 Best Practices:
  • Use real email addresses you have access to
  • Maintain consistent sender names for brand recognition
  • Regularly check and update inactive senders
  • Use role-based addresses sparingly (info@, support@)
⚡ Pro Tips:
  • Create department-specific senders (sales@, support@, newsletter@)
  • Personal senders often have better engagement
  • Test sender reputation regularly

Authorizations

​
X-Team-ApiKey
string
header
required

Team API key for authentication. Find your API key in SendX Settings → Team API Key.

Example:

X-Team-ApiKey: your_team_api_key_here

Body

application/json
​
name
string
required

Sender display name

Example:

"John Smith"

​
email
string<email>
required

Sender email address (must be verified)

Example:

"john@example.com"

Response

✅ Sender created successfully

​
id
string

Unique sender identifier with sender_ prefix

Example:

"sender_4vK3WFhMgvOwUNyaL4QxCD"

​
name
string

Sender display name

Example:

"John Smith"

​
email
string<email>

Sender email address

Example:

"john@example.com"

​
isWhitelisted
boolean

Sender whitelist status

Example:

true

⌘I