For channel providers

Integrate once. Be offered to every business and platform on AuraPost.

For SMS and RCS carriers, WhatsApp routes, email infrastructure and, as the roadmap grows, advertising channels. One adapter, and your service is a route every account can choose, with delivery reports normalised and per-message billing handled.

The queue you skip

No more integrating with one CRM at a time.

A provider's growth is usually gated by how many software platforms it has managed to integrate with. AuraPost inverts that. Platforms integrate with the switchboard; you integrate with the switchboard; everyone on it can reach everyone else.

  • DistributionEvery business and every platform on AuraPost can route through you from day one.
  • Bring-your-own accountsYour existing customers can connect their account with you and keep their rates. You keep the relationship.
  • Configuration, not codeThe vendor layer is driven by a manifest for HTTP APIs: describe your send and delivery-report endpoints and the switchboard does the rest.
Provider manifest · what we need
Send endpoint and authrequired
Delivery-report webhook shaperequired
Rate and concurrency limitsrequired
Price per message, per marketrequired
Sandbox credentials for provingbefore go-live

How routing works

Accounts pick you. Platforms pick you for their merchants. Backups cover you.

Routes per account

A business chooses a route per channel: yours, another provider's, or their own account with you. Most-specific setting wins.

Routes per platform

A software platform sets a default route for all its merchants and can override it for any one of them.

Backup routes and auto-resume

If you are down, a backup takes over and traffic returns when you recover. Incidents are tracked, not hidden.

Normalised delivery reports

Your status codes are mapped once to sent, delivered, failed and expired. Every account sees the same vocabulary.

Billing handled

Per-message pricing from each account's wallet, settled against your rate card. No invoicing of individual merchants.

Measured in production

Delivery rate, latency and failure categories per route, visible to the accounts choosing between routes.

Where we are

Providers join by invitation while the programme opens up.

SMS and RCS routes are live. WhatsApp runs direct to Meta today, with third-party routes on the roadmap. If you carry a channel our accounts need, write to us with the channel and the markets you cover.

support@theaurapost.com

Questions, answered first

Frequently asked questions

What kind of provider can join?

Anyone who carries customer messages: SMS and RCS carriers, WhatsApp routes, email infrastructure and, as the roadmap grows, advertising channels such as Google campaigns.

What does the integration involve?

AuraPost's vendor layer is configuration-driven for HTTP APIs. For most providers that means describing your send and delivery-report endpoints, not writing code on our side or yours.

How do accounts choose a provider?

Accounts can bring their own account with you, or use AuraPost's route. Software platforms can set a route for all their merchants. A backup route takes over if a provider fails.

How do I start?

Providers are onboarded by invitation while the programme opens up. Write to us with the channel you carry and the markets you cover.

One integration. Every account on the switchboard.

Tell us what you carry and where.