Skip to content

Create sender profile

If you have questions regarding this API, please visit our API FAQ page.

Creating a sender profile

Make a POST request to https://webapi.inboxroad.com/api/v2/sender-profiles/ with a valid X-API-Key (see v2 authentication).

Terminal window
curl -X POST 'https://webapi.inboxroad.com/api/v2/sender-profiles/' \
-H 'X-API-Key: <your_token>' \
-H 'Content-Type: application/json' \
-d '{
"name": "Acme Newsletter",
"email": "news@acme.com",
"reply_to": "support@acme.com"
}'

By default the profile sends through Inboxroad’s infrastructure. To send through your own relay instead, include an external_smtp object — this is available to Email Pro customers only; other accounts receive 403.

Request fields

Field nameRequiredDescription
nameYesHuman-readable sender name (max 255 chars, cannot be blank).
emailYesFrom address. Its domain determines the sending domain.
reply_toNoReply-To address.
external_smtpNoCustom SMTP relay. Email Pro customers only (see fields below).

External SMTP fields (external_smtp)

Field nameRequiredDescription
hostYesSMTP host.
portYesSMTP port.
usernameYesSMTP username.
passwordYesSMTP password. Never returned in responses.
providerNoOne of sendgrid, mailgun, amazon_ses, sparkpost, postmark, smtp2go, mailjet, mandrill, brevo, mysmtp, smtpcom, other. Default other.
smtp_nameNoHuman-readable label for the relay.
securityNoTransport security: none, tls, or ssl. Default tls.
bounce_webhook_urlNoURL the provider posts bounce notifications to.
bounce_email_addressNoAddress that receives bounce notifications.

Response

On success the API returns 201 with the created sender profile. See List sender profiles for the object shape.

Possible response codes

Status codeDescription
201Sender profile created successfully.
401Unauthorized.
403external_smtp supplied but the account is not Email Pro. Body: { "errors": [ ... ] }.