Sell data, airtime and checker PINs from your own app.
The PATUpaa API gives approved businesses catalog access, account pricing, single and bulk ordering, wallet funding, order status and webhooks — with the same delivery pipeline as the main platform.
One integration. Every service.
Use the API to power a customer app, a reseller website or an internal operations tool. Approved API accounts get their own pricing, keys, IP allowlist and rate limits.
API capabilities
Fetch networks, data bundles, airtime products and your effective API prices.
Digital gift cards are available too: submit type=digital with the selected account_region, region_confirmed and terms_accepted. Completed orders expose the gift-card code in your order response.
Place one order or submit a batch with row-level idempotency and validation.
Read your balance and fund the business wallet through the supported payment flow.
Track order outcomes and receive signed webhooks instead of polling.
Separate keys for each integration, permission scopes and an IP allowlist.
Manage keys, webhooks, pricing visibility, orders and wallet from one dashboard.
How access works
- 1Create a PATUpaa account and apply for API access.
- 2An administrator reviews the business and sets your API pricing.
- 3Create keys, configure webhooks and start with the catalog endpoint.
- 4Place orders and reconcile outcomes through status or signed webhooks.
You must be signed in to apply. API access and pricing are approved per business account.
API questions
Who can use the API?
Approved businesses and developers. A normal customer account can apply for API access; API accounts do not participate in consumer referral or points benefits.
How do I get credentials?
Apply from your account. Once approved, create API keys in the API portal and store the secret securely — it is shown only once.
How are prices set?
Fallback order is your active customer override, then the standard API price, then the bundle API price. Prices are never below provider cost.
Do you support bulk orders?
Yes. Bulk batches use row-level idempotency so a repeated request cannot charge completed rows twice.