The messaging switchboard
One connection. Every channel. Every provider.
AuraPost sits between your software and your customers. Plug in once and send email, WhatsApp and web push today, with SMS and RCS in early access, plus every channel and provider we connect next, with nothing new to integrate and no add-on to buy.
Building a platform or carrying a channel? Plug your platform in · Offer your channel · Resell as an agency
Diagram: your app, CRM, store and dashboard connect once to AuraPost, which applies fallback chains, frequency caps, consent and wallet rules, then routes each message to email, WhatsApp or web push, with SMS, RCS and Google campaigns in early access.
Three sides. One switchboard.
Everyone plugs in once.
Every messaging product you have seen sells channels one at a time. AuraPost sells the connection between them.
Every channel from one account
One dashboard, one API key, one customer profile. Send a receipt by email, a reminder on WhatsApp, an OTP by SMS and a cart nudge by push. When a new channel or a better provider joins, it appears in your account. No add-on to buy, no vendor to onboard.
Start freePlug in once, every merchant gets everything
A CRM, loyalty, booking, POS or e-commerce platform integrates AuraPost once. Every merchant on it gets every channel, each with its own wallet, limits and WhatsApp number. You stop building channel integrations one vendor at a time.
For platformsIntegrate once, reach every account
A carrier, a WhatsApp route or an email provider connects to AuraPost once and is offered to every business and every platform on it. No queue at each CRM's door, no bespoke integration per customer.
For providersWhy a switchboard
Today every channel is a separate purchase.
Each one means a new vendor, a new contract, a new integration and a new add-on in whatever software you already run. Then you do it again for the next channel.
- 1 Find and sign a vendor
- 2 Build or buy the integration
- 3 Wire delivery reports and consent
- 4 Add it as a paid add-on in your CRM
- 5 Repeat for SMS, RCS, push, the next thing
Five steps, five times. And a merchant still ends up with five logins and five bills.
- 1 Connect once
Every channel that exists, and every one added later, arrives through the same connection with the same contacts, reporting, consent and wallet.
Channels
Three live, three in early access. More on the way.
Each channel is a full product on its own. Together they share one profile, one set of limits and one bill.
Also on the roadmap: a choice of third-party WhatsApp routes alongside the direct Meta connection. Roadmap items are always labelled "coming" on this site.
What happens in the middle
A pipe moves messages. A switchboard decides.
These rules run on every send, on every channel, so adding a channel never adds a risk.
WhatsApp not delivered? SMS goes. Still nothing? Email. In the order you set, stopping at the first delivery, with a cost estimate before you save.
Limits per channel and across channels. A customer is never hit on five channels in one evening, and never at 2 am.
Unsubscribe, STOP, double opt-in, WhatsApp opt-in import and a preference centre, all honoured before a message leaves.
Entities, sender headers and templates registered from the dashboard, with a readiness check that goes green before your first SMS.
Top up once, spend on any channel, see cost by channel. Sending pauses when the balance runs low. WhatsApp is billed at Meta's own price.
Sent, delivered, read, clicked, failed, on every channel, in the same screens, the same webhooks and the same CSV.
For software platforms
Your merchants get every channel. You ship nothing.
Create a messaging account per merchant through the partner API. Each gets its own wallet, limits and WhatsApp number, and a portal on your domain with your brand. When AuraPost adds a channel, it is simply there.
merchant_4821readyFor channel providers
Integrate once. Be offered to everyone.
Carriers, WhatsApp routes and email providers spend years integrating with one CRM after another. Connect to AuraPost once and every business and platform on it can route through you, with delivery reports normalised and billing handled per message.
Developers
One key. Every channel.
Same bearer key, same base URL, a send endpoint per channel. Webhooks for every delivery event, idempotency keys on every send, SDKs for Node.js, PHP and Python.
# email · transactional lane
curl https://theaurapost.com/api/v2/messages/email/send \
-H "Authorization: Bearer $API_KEY" \
-d '{"to":"user@example.com","template":"welcome","subject":"Welcome"}'
# whatsapp · approved template, your own number
curl https://theaurapost.com/api/v2/messages/whatsapp/send \
-H "Authorization: Bearer $API_KEY" \
-H "Idempotency-Key: order-8812" \
-d '{"to":"+919876543210","template":"order_update"}'
# sms (early access) · DLT template, registered header
curl https://theaurapost.com/api/v2/messages/sms/send \
-H "Authorization: Bearer $API_KEY" \
-H "Idempotency-Key: otp-4471" \
-d '{"to":"+919876543210","template":"otp_login","params":{"code":"482913"}}'
# rcs (early access) · rich card, falls back to sms in a chain
curl https://theaurapost.com/api/v2/messages/rcs/send \
-H "Authorization: Bearer $API_KEY" \
-d '{"to":"+919876543210","template":"new_arrivals"}'
# web push · by email, phone or subscriber id
curl https://theaurapost.com/api/v2/push/send \
-H "Authorization: Bearer $API_KEY" \
-d '{"email":"user@example.com","title":"Your order shipped","body":"Track it now"}'
Questions, answered first
What people ask before they plug in
What is AuraPost?
AuraPost is a messaging switchboard. Your software connects to it once, and through that one connection you send email, WhatsApp and web push to your customers today, with SMS and RCS in early access. When a new channel or provider is connected to AuraPost, it becomes available to you without a new integration.
What does "switchboard" mean here?
It means AuraPost sits in the middle. On one side are the businesses and software platforms that need to send messages. On the other side are the channels and the providers that carry them. Each side integrates with AuraPost once instead of with every party on the other side.
Which channels are live today?
Email (on AWS SES), WhatsApp (direct to Meta through Embedded Signup) and web push for e-commerce and ordinary websites are live. SMS and RCS (through DLT-registered vendors, with India DLT handled in-product) are in early access: built and being tested end to end, and not yet open to customers. Google campaigns (running Google Ads from the same switchboard) are also in early access. Additional WhatsApp routes are on the roadmap and are labelled as coming on this site.
Do I need a separate WhatsApp provider (BSP)?
No. You connect your own WhatsApp Business Account to Meta through Embedded Signup inside AuraPost. There is no business solution provider in the middle, so you pay Meta's own conversation price with no markup, and the number stays yours if you ever leave.
I only want one channel. Is this still for me?
Yes. Start with the one channel you need. Every channel has its own page on this site. The difference from a single-channel tool is that the other channels are already in your account when you want them, with the same contacts, reporting and limits.
What happens when a message cannot be delivered?
You set a fallback chain, for example WhatsApp, then SMS, then email. AuraPost tries each in order and stops at the first delivery. Frequency caps and quiet hours apply across the whole chain, so a customer is never hit on every channel at once.
Is there an API?
Yes. One API key covers all channels, with webhooks, idempotency keys and SDKs for Node.js, PHP and Python. The full reference is at /docs.
How is it priced?
Per message, from a prepaid wallet you top up. WhatsApp is billed at Meta's conversation price. Pricing per channel is shown inside your account before you send, and sending pauses automatically when the balance runs low.
Connect once. Never integrate a channel again.
Free to start. No card. Your first channel is live in minutes.