SendLibSendLib
API

Sending domainsv1

Verify a domain so your mail authenticates correctly with DKIM and aligned return-path.

Why this matters

To reliably reach inboxes, you should send from a verified domain. Domain verification typically provisions DNS records for:

  • DKIM
  • Return-path / bounce handling
  • Tracking subdomains (if enabled)

Do this before you ramp volume

Verify your sending domain early so you can warm up reputation gradually.

Endpoints

POST Request
Bearer
POST/v1/sending-domains

Create a sending domain and return required DNS records.

GET Request
Bearer
GET/v1/sending-domains

List sending domains.

GET Request
Bearer
GET/v1/sending-domains/{id}

Get domain details and DNS status.

POST Request
Bearer
POST/v1/sending-domains/{id}/verify

Re-check DNS and update verification state.

PATCH Request
Bearer
PATCH/v1/sending-domains/{id}

Update domain settings (if supported).

DELETE Request
Bearer
DELETE/v1/sending-domains/{id}

Delete a sending domain.

Authentication

  • Required scope: manage:sending-domains

Create a sending domain (example)

bash
curl -sS -X POST https://api.sendlib.com/v1/sending-domains \
  -H "Authorization: Bearer $SENDLIB_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"sending_domain":"example.com"}'

Verify (example)

bash
curl -sS -X POST https://api.sendlib.com/v1/sending-domains/DOMAIN_ID/verify \
  -H "Authorization: Bearer $SENDLIB_API_KEY"

DNS takes time

DNS propagation can take minutes to hours. It's normal for verification to fail until records have propagated.

Next

Previous

Retries & outcomes

Next

Deliverability basics