Environments and access
Aura runs two separate environments. Keys and data never cross between them.
| Environment | Base URL | Keys start | What happens |
|---|---|---|---|
| Sandbox | https://sandbox.api.poweredbyaura.com/v1 |
aura_test_ |
Nothing is delivered or charged. Test numbers produce each outcome on purpose. |
| Production | https://api.poweredbyaura.com/v1 |
aura_live_ |
Real bundles on real numbers, charged to your balance. |
Getting access
Section titled “Getting access”There is no self-service sign-up or dashboard. When your organisation starts an integration:
- Aura assigns your engineering team a technical contact, who stays your route for keys, questions and incidents.
- Your technical contact issues a sandbox key, sets up your webhook endpoint and secret, and agrees any IP allowlist with you.
- Once your integration passes its sandbox tests, your technical contact issues production keys.
To start, use the form at poweredbyaura.com/contact or write to [email protected].
What you need to keep safe
Section titled “What you need to keep safe”- API keys. Keep them on your servers, in a secret store, never in source code, apps or browsers.
- Your webhook secret. It proves that a webhook came from Aura.
How keys are rotated and revoked is in Authentication.
© 2026 Aura Mobile Communications Ltd ·poweredbyaura.com ·Privacy ·Terms