Evaluation questions
These are the questions engineering teams ask first. Each answer is short; the link goes to the detail.
Which networks and bundles are supported, and with what constraints?
Section titled “Which networks and bundles are supported, and with what constraints?”Your catalogue in the API lists every bundle your account can buy, with its network, size, validity and your price. Each network’s constraints, such as which numbers it will credit, are confirmed for your market during an evaluation. See Networks and bundles.
How do we authenticate, and what do requests and responses look like?
Section titled “How do we authenticate, and what do requests and responses look like?”A secret bearer key per environment, optionally limited to your IP addresses. JSON over HTTPS, E.164 phone numbers, money in minor units, timestamps in UTC. See Authentication and the API reference.
What uptime and latency should we expect?
Section titled “What uptime and latency should we expect?”Commitments are set in your agreement. The API reports each network’s live status and its measured time to confirmation, and every purchase carries the latest time it will be final. See Reliability and Service status.
How are asynchronous and pending purchases handled?
Section titled “How are asynchronous and pending purchases handled?”A purchase is accepted at once as pending, then becomes successful or failed when the network answers, and
never later than its resolve_by. Your balance is held, not charged, while it is pending. See
Transaction lifecycle.
What error codes are there?
Section titled “What error codes are there?”One error shape for every endpoint, with a stable code and a retryable flag. See Errors.
How do idempotency and retries work?
Section titled “How do idempotency and retries work?”Your reference is the idempotency key. Retrying with it can never buy twice. See
Idempotency and retries.
How do callbacks and delivery confirmation work?
Section titled “How do callbacks and delivery confirmation work?”Signed webhooks for each final state, retried if your endpoint does not acknowledge. successful means the network
confirmed the credit, and carries the network’s own reference. See Webhooks and
Delivery confirmation.
How do we look up a transaction and reconcile?
Section titled “How do we look up a transaction and reconcile?”Look up any purchase by your reference or Aura’s ID, read your balance, and download each day’s statement as JSON or CSV. See Lookup and reconciliation.
How is the service monitored, and how do we escalate?
Section titled “How is the service monitored, and how do we escalate?”Status is reported inside the API: on each network, in errors, and from a status endpoint. Incidents go through your named technical contact, with the escalation route set in your agreement. See Service status and Support and escalation.
© 2026 Aura Mobile Communications Ltd ·poweredbyaura.com ·Privacy ·Terms