Troubleshooting
| Problem | Likely cause | Fix |
|---|---|---|
401 invalid_api_key on every request |
A sandbox key against production, or the reverse. | Match the key prefix to the base URL. See Authentication. |
403 ip_not_allowed |
Your request left from an address that is not on your allowlist. | Check your outbound address, or ask your technical contact to update the list. |
409 reference_conflict |
You reused a reference for a different purchase. | Use one reference per intended purchase. A retry must send the exact same body. |
422 network_mismatch |
The number has been ported to another network. | Look the number up with Number lookups and pick a bundle for its network. |
A purchase stays pending |
The network is slow to confirm. | Nothing to do. It will be final by resolve_by. Check the network’s status and recent_delivery. |
| No webhook arrives | Your endpoint is unreachable, slow or rejected the signature. | Check your logs for 400s from signature checks, make sure you reply within 10 seconds, then look the purchase up. |
| Signatures never match | The body was parsed and re-serialised before checking. | Verify against the raw request body. See Webhooks. |
| Your totals differ from the statement | A purchase charged just after midnight UTC, or a late reversal. | Match by the day a purchase was charged. See reconciliation. |
Still stuck
Section titled “Still stuck”Send your technical contact:
- the
Aura-Request-Idfrom the response, or therequest_idin the error; - the purchase
idor yourreference; - the environment, and roughly when it happened.
Never send an API key or webhook secret, in email or anywhere else.
© 2026 Aura Mobile Communications Ltd ·poweredbyaura.com ·Privacy ·Terms