Providers
The nine providers you can connect, the channel each serves, what each connect form asks for, and where delivery reports go.
Messaging connects to nine providers. This page lists exactly what the connect form asks for. Fields marked secret are hidden as you type and never shown again. Fields marked required must be filled.
Every connect form also asks for a Name, a sender (From address, From number or Business number) and, for email only, an optional From name.
Summary
| Channel | Provider | What it can do |
|---|---|---|
| Amazon SES | Rich HTML · Delivery reports | |
| Mailgun | Rich HTML · Delivery reports | |
| Postmark | Rich HTML · Delivery reports | |
| Resend | Rich HTML · Delivery reports | |
| SendGrid | Rich HTML · Delivery reports · Reads your templates | |
| SMTP server | Rich HTML | |
| SMS | MSG91 | Templates only · India DLT · Delivery reports |
| SMS | Twilio | Delivery reports · Can receive replies |
| WhatsApp (Meta Cloud API) | Templates only · Reads your templates · Delivery reports · Can receive replies |
"Can receive replies" describes the provider. Replies are not shown in Messaging.
Amazon SES (email)
| Field | Required | Notes |
|---|---|---|
| Access key ID | Yes, secret | Looks like AKIA.... |
| Secret access key | Yes, secret | |
| Region | Yes | For example ap-south-1. |
| Configuration set | No | Required if you want SES to publish delivery events. |
Before you connect: verify your domain or sender address in SES and publish the DKIM records. Create an IAM user with the permissions to send email and list email identities, and use its access key. A brand-new SES account is sandboxed: request production access or every recipient must be verified too.
Delivery reports: in SES, open Configuration sets, then your set, then Event destinations, then Amazon SNS. Create an SNS topic and add an HTTPS subscription pointing at the AxisIQ web address. AxisIQ confirms the subscription automatically.
Mailgun (email)
| Field | Required | Notes |
|---|---|---|
| API key | Yes, secret | Looks like key-.... |
| Sending domain | Yes | For example mg.example.com. |
| Region | No | us (default) or eu. Must match where the domain was created. |
| Webhook signing key | No, secret | From Mailgun's HTTP webhook signing key. |
Before you connect: add and verify your domain in Mailgun, publish its DNS records, then copy the domain's API key. EU-region domains must set Region to eu, or every call fails.
Delivery reports: in Mailgun's Webhooks, point delivered, permanent failure and complained at the AxisIQ web address.
Postmark (email)
| Field | Required | Notes |
|---|---|---|
| Server API token | Yes, secret | |
| Message stream | No | Postmark separates transactional from bulk. Defaults to outbound. |
Before you connect: create a server in Postmark, verify your sender signature or domain, and copy the Server API Token from the API Tokens tab.
Delivery reports: in your Postmark server's Webhooks, enable Delivery, Bounce and Spam Complaint.
Resend (email)
| Field | Required | Notes |
|---|---|---|
| API key | Yes, secret | Looks like re_.... |
| Webhook signing secret | No, secret | From Webhooks, your endpoint. Without it, callbacks are accepted on the web address's secret alone. |
Before you connect: verify your sending domain in Resend (Domains, then Add domain, then publish the DKIM records it shows). Create an API key with Sending access. The From address must be on the verified domain.
Delivery reports: in Resend's Webhooks, add an endpoint and subscribe to email.sent, email.delivered, email.bounced and email.complained.
SendGrid (email)
| Field | Required | Notes |
|---|---|---|
| API key | Yes, secret | Looks like SG.... |
Before you connect: authenticate your domain in SendGrid (Settings, then Sender Authentication) and publish the CNAMEs it gives you. Create an API key with Mail Send permission.
Delivery reports: in SendGrid's Mail Settings, Event Webhook, enable delivered, bounced, dropped and spam report. Signature verification is not used: the secret in the web address authenticates the callback.
SendGrid can also load its own templates. See Templates.
SMTP server (email)
| Field | Required | Notes |
|---|---|---|
| Host | Yes | For example smtp.example.com. |
| Port | Yes | 587 for STARTTLS, 465 for implicit TLS. |
| Username | No, secret | |
| Password | No, secret |
Before you connect: any SMTP relay works. TLS is required: port 465 connects over TLS directly, and anything else must offer STARTTLS. Plaintext SMTP is refused.
Delivery reports: none. SMTP reports nothing back, so a message stops at Sent.
Twilio (SMS)
| Field | Required | Notes |
|---|---|---|
| Account SID | Yes | Looks like AC.... |
| Auth token | Yes, secret | |
| Messaging Service SID | No | If set, Twilio picks the sender from that service's pool instead of the From number. |
Before you connect: buy or verify a number in Twilio, then copy the Account SID and Auth Token from the console. For volume, create a Messaging Service and paste its SID: Twilio then handles sender rotation and opt-outs.
Delivery reports: in Twilio, set your number's (or Messaging Service's) Status callback URL to the AxisIQ web address.
MSG91 (SMS, India)
| Field | Required | Notes |
|---|---|---|
| Auth key | Yes, secret | |
| Sender ID | Yes | Your DLT-registered six-character header, for example AXISIQ. |
Before you connect: Indian SMS is governed by TRAI's DLT registry. Register your entity, your header (sender ID) and every message template with your operator, then approve them inside MSG91. A template in AxisIQ must carry the DLT template ID as its provider reference, because MSG91 will not send free-form text.
Delivery reports: in MSG91, open Settings, then Webhooks, then delivery reports, and point them at the AxisIQ web address.
WhatsApp (Meta Cloud API)
| Field | Required | Notes |
|---|---|---|
| Access token | Yes, secret | A permanent System User token. A temporary one from the dashboard expires in 24 hours. |
| Phone number ID | Yes | Not the phone number: the numeric ID beside it in WhatsApp Manager. |
| WhatsApp Business Account ID | No | Needed to read your approved templates. |
| App secret | No, secret | From the Meta app's Settings, Basic. Used to verify callback signatures. |
| Webhook verify token | No | Any string you choose. Meta asks for it once when you subscribe. |
Before you connect: in Meta Business, create an app with the WhatsApp product, add and verify your business phone number, and create a System User with a permanent token holding whatsapp_business_messaging and whatsapp_business_management. Every message you send outside a customer-initiated 24-hour window must use a template Meta has approved.
Delivery reports: in the Meta app, open WhatsApp, then Configuration, then Webhook. Paste the AxisIQ web address and your verify token, then subscribe to the messages field.