Vend data bundles via sub account (v1)
Deprecated. This endpoint is deprecated and will be removed in a future release. Use POST /v2/bill/data/{subAccountId} instead.
Authorizations
Nomba authenticates API calls with OAuth2 HTTP bearer tokens. There are two methods of authentication; Client-Credentials method and PKCE (Proof Key for Code Exchange) method. In each of the methods, You will get an ACCESS_TOKEN. You need to use an "Authorization" HTTP header to provide your ACCESS_TOKEN. For example: Authorization: {ACCESS_TOKEN}.
Headers
The parent accountId of the business this sub account belongs to
"890022ce-bae0-45c1-9b9d-ee7872e6ca27"
Path Parameters
The sub accountId via which data bundle is to be vended
"890022ce-bae0-45c1-9b9d-ee7872e6ca27"
Body
The request payload required to vend data bundles
The unique identifier of the data plan to purchase — returned as productId by the Fetch Data Plans endpoint. Required for all new integrations: it resolves to an exact plan and amount, removing any ambiguity when multiple plans on the same network share the same price.
"mtn47"
Recipient phone number
11 - 13"08055441122"
Recipient network (telco). It can also come as lowercased values e.g. glo, mtn etc.
GLO, MTN, 9MOBILE, AIRTEL 3"GLO"
Merchant Transaction Identifier reference (Unique to merchant)
"3bvwhibh38220dsjakTwvb"
Deprecated — do not use. amount is a legacy-only field with no guarantee of correctness: multiple plans can share the same price, so it cannot reliably identify the bundle you want. Use productId — the only supported way to select a plan.
A name to describe the sender of the data
"John Doe"