Skip to main content
Every client needs an active GBP FX wallet in the calling key’s mode. Purchases debit that wallet regardless of the business’s country. Fund your GBP wallet through Dashboard → Accounts before purchasing. GBP funding is dashboard-only; there is no public GBP conversion API. Existing local NGN airtime, data and bill-payment APIs remain separate services.
Signature required: No for these discovery requests. They require X-Numero-Api-Key and vas:write.
Signature required: Yes for quote, purchase, status and delivery. Send X-Numero-Api-Key, X-Numero-Signature and X-Numero-Signature-Version: v2 on these requests, using the signing rules. All endpoints on this page require vas:write.

​
Discover and quote

Service codes are GLOBALAIRTIME, GLOBALDATA, GIFTCARD and UTILITY. Check access, list countries with ?serviceCode=…, then request products with serviceCode, two-letter countryCode and optional page. Select a currently returned product and denomination; do not assume that every product is available in every destination country. Quote with serviceCode, countryCode, productId, amount and recipient. Gift cards also require senderName; utility products may require invoiceId, productUserId or amountId according to the selected product. The recipient is an international phone number, recipient email or subscriber account number as appropriate. Gift-card amounts use the product’s recipient currency. Airtime/data/utility request amounts use GBP. The quote returns amount, fee, total and currency: GBP; use that exact total when reviewing the GBP debit. See the OpenAPI request model for field limits.

​
Purchase once and track delivery

Purchase requires Idempotency-Key. Send the quoted request, a unique Numero transaction reference, and expectedTotal equal to the quoted GBP total. Preserve the key, reference and exact body when retrying after an uncertain response. A stale total must be requoted rather than silently changing the debit. Poll status and delivery using ?reference=…. An accepted or pending request does not establish fulfilment. Corporate API approval rules, when opted in, can return a pending approval before purchase execution; use the GLOBAL_VAS rail with approval status. Keep gift-card delivery data private. Read it only through the authenticated delivery endpoint after successful fulfilment. Never expose delivery codes in logs or public webhook URLs. Provider webhook delivery is handled by Numero; API clients configure their own business webhooks through the normal Numero subscription flow. Test-key simulations are isolated from real provider purchases. A simulated success does not prove provider float, fulfilment or a real upstream callback.