# Sakawave API

> Build accounts, transfers, and transaction reconciliation with Sakawave.

- [Sakawave API](https://docs.sakawave.com/introduction.md): Build customer wallets, move money, and reconcile transactions with the Sakawave Business API.
- [Quickstart](https://docs.sakawave.com/quickstart.md): Authenticate and read your first page of Sakawave accounts in under ten minutes.
- [Authentication](https://docs.sakawave.com/guides/authentication.md): Create, store, restrict, rotate, and revoke Sakawave API keys.
- [Environments](https://docs.sakawave.com/guides/environments.md): Keep sandbox and live credentials, data, and webhook configuration isolated.
- [Money and currencies](https://docs.sakawave.com/guides/money-and-currencies.md): Represent Sakawave monetary values without rounding or precision loss.
- [Transfer corridors and recipients](https://docs.sakawave.com/guides/transfer-corridors-and-recipients.md): Discover payout fields, save reusable recipient resources, and create provider-neutral transfer destinations.
- [Pagination, filtering, and sorting](https://docs.sakawave.com/guides/pagination-filtering-sorting.md): Page through collections and apply validated filters and sort expressions.
- [Errors](https://docs.sakawave.com/guides/errors.md): Handle Sakawave error envelopes and machine-readable codes.
- [Rate limits](https://docs.sakawave.com/guides/rate-limits.md): Understand limits and implement safe, jittered backoff.
- [Versioning](https://docs.sakawave.com/guides/versioning.md): Understand the current version boundary and pending compatibility policy.
- [Currencies and countries overview](https://docs.sakawave.com/services/currencies/overview.md): The four pieces of reference data every money movement reads, and how they compose.
- [Currencies and countries introduction](https://docs.sakawave.com/services/currencies/introduction.md): Why reference data is worth reading first, and what it saves you.
- [Get started with currencies and countries](https://docs.sakawave.com/services/currencies/get-started.md): Ask what you can open an account in, then what can deliver to a destination — in two calls.
- [Currencies and countries setup and configuration](https://docs.sakawave.com/services/currencies/setup-and-configuration.md): Auth, caching, rate limits, and what to do when reference data changes underneath you.
- [Currencies and countries use cases](https://docs.sakawave.com/services/currencies/use-cases.md): Four flows — building pickers, driving a payout form from field descriptors, prechecking a transfer, and keeping a cache honest.
- [Capabilities and corridors](https://docs.sakawave.com/services/currencies/capabilities-and-corridors.md): The six currency switches, which one is checked where, and how routes and FX corridors decide whether money can actually move.
- [Customers overview](https://docs.sakawave.com/services/customers/overview.md): What a Sakawave customer is, which fields it holds, and how it moves through its lifecycle.
- [Customers introduction](https://docs.sakawave.com/services/customers/introduction.md): The problem the Customers service solves, when to use it, and what it deliberately leaves to you.
- [Get started with customers](https://docs.sakawave.com/services/customers/get-started.md): Create your first customer and read it back, in under ten minutes.
- [Customers setup and configuration](https://docs.sakawave.com/services/customers/setup-and-configuration.md): Credentials, environments, limits, webhooks, and the prerequisites the service enforces before it accepts a call.
- [Customer use cases](https://docs.sakawave.com/services/customers/use-cases.md): Four complete integrations — onboarding, keeping records in step, finding customers, and offboarding — with the error branches that actually occur.
- [Identity and verification](https://docs.sakawave.com/services/customers/identity-and-verification.md): Which identity numbers a customer can hold, how they are stored, and what tier 1 does and does not permit.
- [Accounts overview](https://docs.sakawave.com/services/accounts/overview.md): What a Sakawave account is, the flags that govern it, and how funding destinations attach to it.
- [Accounts introduction](https://docs.sakawave.com/services/accounts/introduction.md): Why accounts exist, the difference between your money and your customers' money, and how many accounts to open.
- [Get started with accounts](https://docs.sakawave.com/services/accounts/get-started.md): Open an NGN account, give it a payable destination, and confirm it can reach the outside world.
- [Accounts setup and configuration](https://docs.sakawave.com/services/accounts/setup-and-configuration.md): What is checked when an account opens, when its details are issued, and when money moves; rate limits, webhook wiring, and what has to be true before your first call.
- [Account use cases](https://docs.sakawave.com/services/accounts/use-cases.md): Four flows — opening a payable account, giving customers wallets, separating your money from theirs, and reconciling balances.
- [Currencies and funding rails](https://docs.sakawave.com/services/accounts/currencies-and-funding-rails.md): Which assets an account can hold, what each one requires, and how money physically reaches it.
- [Recipients and destinations overview](https://docs.sakawave.com/services/recipients/overview.md): The two objects that answer "where is this money going", how they differ, and why one of them expires.
- [Recipients and destinations introduction](https://docs.sakawave.com/services/recipients/introduction.md): Why a transfer needs a destination rather than an account number, and when to save a recipient.
- [Get started with recipients and destinations](https://docs.sakawave.com/services/recipients/get-started.md): Save a recipient, give them routing, and turn them into a spendable destination.
- [Recipients and destinations setup and configuration](https://docs.sakawave.com/services/recipients/setup-and-configuration.md): Rate limits shared across eleven operations, what Sakawave stores, and designing around a 24-hour window.
- [Recipient and destination use cases](https://docs.sakawave.com/services/recipients/use-cases.md): Four flows — recurring payouts, one-off transfers, paying inside Sakawave, and rotating a bank account.
- [Routing fields and verification](https://docs.sakawave.com/services/recipients/routing-fields-and-verification.md): Building a payment payload from a route's field descriptors, what gets verified, and how the two field styles differ.
- [Transfers overview](https://docs.sakawave.com/services/transfers/overview.md): The object that moves money, the seven states it can be in, and where FX quotes fit.
- [Transfers introduction](https://docs.sakawave.com/services/transfers/introduction.md): Why moving money takes several calls, what each one buys you, and which failures happen where.
- [Get started with transfers](https://docs.sakawave.com/services/transfers/get-started.md): Move money between two of your own NGN accounts, end to end, in three calls.
- [Transfers setup and configuration](https://docs.sakawave.com/services/transfers/setup-and-configuration.md): Approval policy, tier limits, one shared rate limit, and the webhooks that tell you what happened.
- [Transfer use cases](https://docs.sakawave.com/services/transfers/use-cases.md): Four flows — a payout batch, retrying safely, watching a transfer to completion, and reconciling against the ledger.
- [Cross-currency transfers](https://docs.sakawave.com/services/transfers/cross-currency-transfers.md): How a quote binds to a transfer, what has to line up, and the order of operations that works.
- [Wallet payouts](https://docs.sakawave.com/services/transfers/wallet-payouts.md): Send USDC from a USDC account to a wallet address on Base, Polygon, Ethereum or Solana.
- [Cards overview](https://docs.sakawave.com/services/cards/overview.md): USD virtual and disposable cards — what they are, the nine states they move through, and the two objects that describe their activity.
- [Cards introduction](https://docs.sakawave.com/services/cards/introduction.md): What card issuance is for, the two tier gates in front of it, and why one of them cannot currently be satisfied.
- [Get started with cards](https://docs.sakawave.com/services/cards/get-started.md): Issue a card, fund it, read its balance and spending — and what to expect at each step.
- [Cards setup and configuration](https://docs.sakawave.com/services/cards/setup-and-configuration.md): Feature gates, the shared idempotency namespace, provider dependence, and the webhooks that report spending.
- [Card use cases](https://docs.sakawave.com/services/cards/use-cases.md): Four flows — issuing a controlled card, topping up, responding to suspected fraud, and reconciling spending.
- [Card programs and PAN handling](https://docs.sakawave.com/services/cards/card-programs-and-pan-handling.md): Choosing a card type, setting controls that hold, and handling the one response in the API that contains a real card number.
- [Bill payments overview](https://docs.sakawave.com/services/bill-payments/overview.md): The catalog, the enquiry, and the payment — three objects and one strict order.
- [Bill payments introduction](https://docs.sakawave.com/services/bill-payments/introduction.md): What the enquiry protects against, how bills differ from transfers, and when the service is the wrong tool.
- [Get started with bill payments](https://docs.sakawave.com/services/bill-payments/get-started.md): Browse the catalog, validate a customer, pay, and read the token — four calls.
- [Bill payments setup and configuration](https://docs.sakawave.com/services/bill-payments/setup-and-configuration.md): Account requirements, the ten-minute window, idempotency, and how pending payments resolve themselves.
- [Bill payment use cases](https://docs.sakawave.com/services/bill-payments/use-cases.md): Four flows — a checkout, airtime top-up, handling a pending vend, and reconciling a day of bills.
- [Airtime, data, and utilities](https://docs.sakawave.com/services/bill-payments/airtime-data-and-utilities.md): How the product families differ in what they need, what they return, and how they fail.
- [eSIM overview](https://docs.sakawave.com/services/esim/overview.md): A catalog priced in USD, a quote in your currency, and a profile someone installs on a phone.
- [eSIM introduction](https://docs.sakawave.com/services/esim/introduction.md): Why the quote exists, how eSIMs differ from bill payments, and when this is the wrong service.
- [Get started with eSIM](https://docs.sakawave.com/services/esim/get-started.md): Browse, quote, buy, and hand over a QR code — four calls.
- [eSIM setup and configuration](https://docs.sakawave.com/services/esim/setup-and-configuration.md): Accounts, the quote window, idempotency, and how failures return money on their own.
- [eSIM use cases](https://docs.sakawave.com/services/esim/use-cases.md): Four flows — a travel checkout, topping up instead of reselling, warning before the data runs out, and reconciling a month.
- [Installation and device support](https://docs.sakawave.com/services/esim/installation-and-device-support.md): What an activation code is, why a QR cannot be scanned from the screen showing it, and how to treat the credential.
- [Create a customer and account](https://docs.sakawave.com/tutorials/create-customer-and-account.md): Create an individual customer, then open an NGN wallet account for that customer.
- [Make a transfer](https://docs.sakawave.com/tutorials/make-a-transfer.md): Resolve a destination, quote or preview the transfer, create it idempotently, and monitor completion.
- [Sell an eSIM](https://docs.sakawave.com/tutorials/sell-an-esim.md): Mirror the catalog, quote in your customer's currency, order idempotently, wait for provisioning, hand over the install details, and run the profile for the rest of its life.
- [Reconcile transactions](https://docs.sakawave.com/tutorials/reconcile-transactions.md): Match transfers to ledger entries and safely handle reversals.
- [Webhooks overview](https://docs.sakawave.com/webhooks/overview.md): How Sakawave tells you something happened — the envelope, the headers, and the one delivery attempt you get.
- [Webhooks introduction](https://docs.sakawave.com/webhooks/introduction.md): What webhooks are good for, what they must not be trusted with, and how they pair with reconciliation.
- [Get started with webhooks](https://docs.sakawave.com/webhooks/get-started.md): Stand up a receiver that verifies, deduplicates, acknowledges fast, and does the work afterwards.
- [Webhooks setup and configuration](https://docs.sakawave.com/webhooks/setup-and-configuration.md): What Sakawave will accept as an endpoint, how the secret works, and every control that lives in the dashboard.
- [Webhook use cases](https://docs.sakawave.com/webhooks/use-cases.md): Four patterns — reacting fast without trusting the event, reconciling what was missed, routing across services, and surviving a rotation.
- [Webhook events](https://docs.sakawave.com/webhooks/events.md): The event catalog, the delivery envelope, and the payload each event family carries.
- [Verify webhook signatures](https://docs.sakawave.com/webhooks/verify-signatures.md): Verify Sakawave signatures against the exact raw request body in Node.js and Python.
- [Testing and resends](https://docs.sakawave.com/webhooks/testing-and-resends.md): Test endpoint delivery, inspect history, and recover failed webhook attempts.
- [List currencies](https://docs.sakawave.com/api-reference/currencies-and-countries/list-currencies.md): Every active currency and the six switches that decide what it can be used for, sorted by code. Filter by a capability to ask a narrower question: "what can I open an account in?" rather than "what exists?".
- [List routes for a currency](https://docs.sakawave.com/api-reference/currencies-and-countries/list-routes-for-a-currency.md): Active payout routes that can deliver to this destination currency, default first. A route carries the `routeId` and the exact field descriptors you need to build a payment detail or an external destination.
- [Discover transfer corridors](https://docs.sakawave.com/api-reference/currencies-and-countries/discover-transfer-corridors.md): Returns active provider-neutral payout routes and their exact client field descriptors. Provider identity is never returned.
- [List countries](https://docs.sakawave.com/api-reference/currencies-and-countries/list-countries.md): Every country Sakawave will onboard, alphabetically by name. This is the source for any `jurisdiction` or `address.country` value you send. Jurisdictions the platform will not serve are absent from the list.
- [List customers](https://docs.sakawave.com/api-reference/customers/list-customers.md): Returns customers belonging to the authenticated business, newest first. Archived customers are never included. An unknown filter or sort key is rejected by name rather than ignored, so a typo cannot silently widen a result set.
- [Create a customer](https://docs.sakawave.com/api-reference/customers/create-a-customer.md): Creates an individual or business customer. `type` selects which fields apply and cannot be changed afterwards. Identity numbers are accepted but never returned: the response reports presence through the `has*` flags. Every customer is created at tier 1.
- [Get a customer](https://docs.sakawave.com/api-reference/customers/get-a-customer.md): Returns one customer belonging to the authenticated business. An archived customer answers 404.
- [Update a customer](https://docs.sakawave.com/api-reference/customers/update-a-customer.md): Updates one or more mutable fields. Send only what changes; at least one field is required. `type` and `jurisdiction` are fixed at creation. Sending a field that belongs to the other customer type is refused rather than ignored.
- [Archive a customer](https://docs.sakawave.com/api-reference/customers/archive-a-customer.md): Archives a customer. The record is retained and hidden: it disappears from reads, and its `externalReference` and identity numbers become reusable. Close the customer’s wallet accounts and terminate their cards first.
- [List accounts](https://docs.sakawave.com/api-reference/accounts/list-accounts.md): Returns your accounts and your customers’ wallet accounts, newest first. Internal platform balances, such as card settlement accounts, are never included. Closed accounts are.
- [Open an account](https://docs.sakawave.com/api-reference/accounts/open-an-account.md): Opens an account for your business, or — when `customerId` is supplied — a wallet account for that customer. The account opens `active` with a zero balance and a freshly minted transfer tag. It cannot yet send or receive externally: issue a detail first.
- [Get an account](https://docs.sakawave.com/api-reference/accounts/get-an-account.md): Returns one account together with every funding and payout detail issued for it. This is the only read that includes `details`; the list endpoint does not.
- [List account details](https://docs.sakawave.com/api-reference/accounts/list-account-details.md): Returns every funding or payout detail issued for an account. An account with none returns an empty array; a guessed identifier returns 404 rather than an empty array, so the response cannot be used to probe for accounts.
- [Issue account detail](https://docs.sakawave.com/api-reference/accounts/issue-account-detail.md): Requests a bank or blockchain funding detail. Provisioning can complete asynchronously.
- [Get account detail](https://docs.sakawave.com/api-reference/accounts/get-account-detail.md): Returns one issued funding or payout detail. The detail must belong to the named account.
- [Create a transfer destination](https://docs.sakawave.com/api-reference/transfer-destinations/create-a-transfer-destination.md): Resolves where money is going, and proves it can get there. `type` selects one of three shapes: your own account, a Sakawave tag, or an external account described inline. The result expires after 24 hours and can be spent once.
- [Create a destination from a recipient](https://docs.sakawave.com/api-reference/transfer-destinations/create-a-destination-from-a-recipient.md): Resolves a saved recipient into a destination you can spend. Omit `paymentDetailId` to use the recipient’s default. Like every destination, the result expires after 24 hours and can be spent once.
- [List transfer recipients](https://docs.sakawave.com/api-reference/transfer-destinations/list-transfer-recipients.md): Every active saved recipient, each with its payment details inlined. Deleted recipients are never returned.
- [Create a transfer recipient](https://docs.sakawave.com/api-reference/transfer-destinations/create-a-transfer-recipient.md): Creates a provider-neutral recipient identity — who you are paying, not how. Routing comes next, as one or more payment details. A recipient with no details cannot be paid.
- [Get a transfer recipient](https://docs.sakawave.com/api-reference/transfer-destinations/get-a-transfer-recipient.md): One active saved recipient, with its payment details inlined. A deleted recipient answers 404.
- [Delete a transfer recipient](https://docs.sakawave.com/api-reference/transfer-destinations/delete-a-transfer-recipient.md): Deactivates the recipient and its payment details. The record is hidden rather than erased: transfers already made keep their masked snapshot of where the money went.
- [List recipient payment details](https://docs.sakawave.com/api-reference/transfer-destinations/list-recipient-payment-details.md): Every active payment detail for one recipient, masked. Raw routing values are encrypted at rest and are never returned by any endpoint.
- [Add recipient payment detail](https://docs.sakawave.com/api-reference/transfer-destinations/add-recipient-payment-detail.md): Adds routing to a recipient: which route, and the exact fields that route requires. Values are validated against the route’s own field descriptors, then encrypted. Only a masked identifier ever comes back.
- [Get recipient payment detail](https://docs.sakawave.com/api-reference/transfer-destinations/get-recipient-payment-detail.md): One masked payment detail. The detail must belong to the named recipient.
- [Set default payment detail](https://docs.sakawave.com/api-reference/transfer-destinations/set-default-payment-detail.md): Makes this detail the recipient’s default — the one used when a destination is created without naming a detail. The previous default is demoted in the same transaction.
- [Delete recipient payment detail](https://docs.sakawave.com/api-reference/transfer-destinations/delete-recipient-payment-detail.md): Deactivates one payment detail. Transfers already made keep their masked snapshot of it.
- [Create an FX quote](https://docs.sakawave.com/api-reference/fx-quotes/create-an-fx-quote.md): Locks a rate for one cross-currency transfer. A quote is bound to the account, destination, side, and amount it was created for, expires at a time the provider sets, and can be spent once.
- [Get an FX quote](https://docs.sakawave.com/api-reference/fx-quotes/get-an-fx-quote.md): One quote, its rate, its expiry, and whether it has been spent.
- [Preview a transfer](https://docs.sakawave.com/api-reference/transfers/preview-a-transfer.md): Runs every check a transfer runs, and moves no money. Returns the amounts, the fee, the total debit, and the route that would be used. Same request body as creating a transfer, minus `externalReference` and `narration`.
- [Create a transfer](https://docs.sakawave.com/api-reference/transfers/create-a-transfer.md): Spends a destination and moves money. Returns as soon as the transfer has a status, which for most transfers means `pending` rather than `completed` — settlement finishes asynchronously and is reported by webhook.
- [List transfers](https://docs.sakawave.com/api-reference/transfers/list-transfers.md): Transfers belonging to your business, newest first. Each item carries a snapshot of where the money went, so a deleted recipient does not erase the history.
- [Get a transfer](https://docs.sakawave.com/api-reference/transfers/get-a-transfer.md): One transfer, with its source account and the provider reference where one exists. This is the authority on a transfer’s state — prefer it over a webhook payload when the two disagree.
- [List cards](https://docs.sakawave.com/api-reference/cards/list-cards.md): Cards belonging to your business. Each item carries its balance, holder, and operation history.
- [Issue a card](https://docs.sakawave.com/api-reference/cards/issue-a-card.md): Issues a USD card and funds it in one call. Returns as soon as issuance is under way — the card starts in `creating` and becomes `active` once the provider has issued it.
- [Get a card](https://docs.sakawave.com/api-reference/cards/get-a-card.md): One card, its balance, its holder, and every operation recorded against it.
- [Create a card FX quote](https://docs.sakawave.com/api-reference/cards/create-a-card-fx-quote.md): Locks a rate for funding a card from a non-USD account, or for withdrawing to one. Amounts are always expressed in USD minor units, whichever direction you are going.
- [Fund a card](https://docs.sakawave.com/api-reference/cards/fund-a-card.md): Moves USD from one of your accounts onto a card. Returns the operation, which may still be `pending` while the provider settles it.
- [Withdraw from a card](https://docs.sakawave.com/api-reference/cards/withdraw-from-a-card.md): Moves USD off a card back to one of your accounts. The mirror of funding, and subject to the same quote rules.
- [Freeze a card](https://docs.sakawave.com/api-reference/cards/freeze-a-card.md): Stops the card authorising payments. Funding and withdrawal still work while frozen, and the card can be unfrozen.
- [Unfreeze a card](https://docs.sakawave.com/api-reference/cards/unfreeze-a-card.md): Returns a frozen card to `active`.
- [Terminate a card](https://docs.sakawave.com/api-reference/cards/terminate-a-card.md): Ends the card permanently and sweeps its remaining balance. The card is frozen first, moves to `terminating`, and reaches `terminated` once the sweep settles.
- [Reveal card credentials](https://docs.sakawave.com/api-reference/cards/reveal-card-credentials.md): Returns the full card number and security code, fetched live from the provider. Sakawave does not store them.
- [List card transactions](https://docs.sakawave.com/api-reference/cards/list-card-transactions.md): Payments made with the card, newest first. Sakawave refreshes from the provider on each call, so this reflects authorisations the ledger has not yet seen.
- [List biller groups](https://docs.sakawave.com/api-reference/bill-payments/list-biller-groups.md): The top of the catalog: the kinds of bill that can be paid — airtime, data, electricity, cable TV and the rest.
- [Get a biller group](https://docs.sakawave.com/api-reference/bill-payments/get-a-biller-group.md): One group by id — for re-resolving an id you stored without walking the catalog.
- [List billers in a group](https://docs.sakawave.com/api-reference/bill-payments/list-billers-in-a-group.md): The billers inside one group — the individual utilities, networks and merchants you can pay.
- [Get a biller in a group](https://docs.sakawave.com/api-reference/bill-payments/get-a-biller-in-a-group.md): One biller by id, asserting it belongs to the group named.
- [List packages for a biller in a group](https://docs.sakawave.com/api-reference/bill-payments/list-packages-for-a-biller-in-a-group.md): The packages a biller offers, asserting the biller belongs to the group named.
- [Get a biller](https://docs.sakawave.com/api-reference/bill-payments/get-a-biller.md): One biller by id, without naming a group.
- [List packages for a biller](https://docs.sakawave.com/api-reference/bill-payments/list-packages-for-a-biller.md): The packages a biller offers, without naming a group.
- [Get a package](https://docs.sakawave.com/api-reference/bill-payments/get-a-package.md): One package by id — for re-resolving an id you stored.
- [Validate a customer](https://docs.sakawave.com/api-reference/bill-payments/validate-a-customer.md): Asks the biller who this customer is and what they owe. An enquiry is required before a payment and is valid for **ten minutes**.
- [Pay a bill](https://docs.sakawave.com/api-reference/bill-payments/pay-a-bill.md): Spends an enquiry and pays the biller. The debit happens immediately; delivery of the value can take longer, so the payment often comes back `submitted` or `pending` rather than `confirmed`.
- [List bill payments](https://docs.sakawave.com/api-reference/bill-payments/list-bill-payments.md): Bill payments made by your business, newest first.
- [Get a bill payment](https://docs.sakawave.com/api-reference/bill-payments/get-a-bill-payment.md): One bill payment, including its token where the biller issued one.
- [List destinations](https://docs.sakawave.com/api-reference/esim/list-destinations.md): Where an eSIM can be used: single countries, multi-country bundles, and the worldwide plan.
- [List plans for a destination](https://docs.sakawave.com/api-reference/esim/list-plans-for-a-destination.md): The data plans available for one destination, cheapest first.
- [Get a plan](https://docs.sakawave.com/api-reference/esim/get-a-plan.md): One plan, with the full list of countries it covers.
- [Quote a purchase](https://docs.sakawave.com/api-reference/esim/quote-a-purchase.md): What a plan costs from a particular account, holding the exchange rate when that account is not USD.
- [Buy an eSIM](https://docs.sakawave.com/api-reference/esim/buy-an-esim.md): Debits the account and orders the eSIM. The debit is immediate; the profile usually arrives within seconds.
- [List your eSIMs](https://docs.sakawave.com/api-reference/esim/list-your-esims.md): Every eSIM this business holds, newest first.
- [List eSIM orders](https://docs.sakawave.com/api-reference/esim/list-esim-orders.md): Purchases and top-ups, with what each one cost.
- [Get an eSIM order](https://docs.sakawave.com/api-reference/esim/get-an-esim-order.md): One order. Poll this while it is `provisioning` if you are not taking webhooks.
- [Get an eSIM](https://docs.sakawave.com/api-reference/esim/get-an-esim.md): One eSIM, with its data allowance and validity as last synchronised.
- [Get install details](https://docs.sakawave.com/api-reference/esim/get-install-details.md): Everything a device needs to install the eSIM, in the three forms a device accepts.
- [Get live usage](https://docs.sakawave.com/api-reference/esim/get-live-usage.md): Data used and validity remaining, refreshed from the network when the stored figure is stale.
- [Quote a top-up](https://docs.sakawave.com/api-reference/esim/quote-a-top-up.md): What adding more data to an existing eSIM would cost.
- [Add data to an eSIM](https://docs.sakawave.com/api-reference/esim/add-data-to-an-esim.md): Extends an eSIM the traveller has already installed. Nothing is reinstalled.
- [Cancel an unused eSIM](https://docs.sakawave.com/api-reference/esim/cancel-an-unused-esim.md): Cancels an eSIM that has never been used, and refunds it.
- [Pause an eSIM](https://docs.sakawave.com/api-reference/esim/pause-an-esim.md): Stops the eSIM carrying data, reversibly. No money moves.
- [Resume a paused eSIM](https://docs.sakawave.com/api-reference/esim/resume-a-paused-esim.md): Undoes a pause. The allowance and expiry are unchanged.
- [Revoke an eSIM](https://docs.sakawave.com/api-reference/esim/revoke-an-esim.md): Tears the eSIM down permanently. Nothing is refunded.
- [Push a message to an eSIM](https://docs.sakawave.com/api-reference/esim/push-a-message-to-an-esim.md): Pushes a short message to the device holding the eSIM. One-way: the eSIM carries no phone number, so the recipient cannot reply and nothing reports back that the message arrived.
- [List messages sent to an eSIM](https://docs.sakawave.com/api-reference/esim/list-messages-sent-to-an-esim.md): What has been pushed to this eSIM, newest first. Refused attempts are kept alongside delivered ones.
- [List transactions](https://docs.sakawave.com/api-reference/transactions/list-transactions.md): Returns ledger transactions belonging to the authenticated business.
- [Get a transaction](https://docs.sakawave.com/api-reference/transactions/get-a-transaction.md): Returns a transaction and its related transfer, bill payment, card payment, or card operation when available.

## OpenAPI Specs

- [openapi-3.0](/openapi-3.0.json)
- [openapi](/openapi.json)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.