Reserved targets

Six numbers for airtime, data and cable TV, mirroring the meters.

In test mode these are the only targets that work. Anything else is refused with "This is not one of the sandbox test targets."

TargetVerifyOrderEnds as
08000000001passes202delivered
08000000002passes422, order in datarefunded
08000000003passes422, data is nullnothing is created
08000000004passes202processing, then delivered after 15s
08000000005passes202processing, then refunded after 15s
08000000006failsnot orderablen/a

They map one to one onto the reserved meters, so whatever you learned there applies here.

Use any provider_id above zero and either an amount above zero or a plan_id. The sandbox does not check that the provider or plan exists, so you can test the flow before you have read the catalogue. Read it anyway: live mode does check, and the ids you will use in production come from there.

Airtime

Airtime, priced by amountbash
curl https://stagingapi.getelectric.ng/api/v2/reseller/orders \
  -H 'Authorization: Bearer <your-test-key>' \
  -H 'Content-Type: application/json' \
  -d '{
    "reference": "sandbox-airtime-001",
    "service": "airtime",
    "provider_id": 3,
    "target": "08000000001",
    "amount": 500
  }'

No verification step. No token on delivery either: airtime, data and cable TV never carry one, in test mode or live.

Data

A bundle, priced by planbash
curl https://stagingapi.getelectric.ng/api/v2/reseller/orders \
  -H 'Authorization: Bearer <your-test-key>' \
  -H 'Content-Type: application/json' \
  -d '{
    "reference": "sandbox-data-001",
    "service": "data",
    "provider_id": 3,
    "plan_id": 184,
    "target": "08000000001"
  }'

Cable TV

Cable TV needs a lookup first. Sandbox target verify returns a fixed customer:

Sandbox target verifyjson
{
  "customer_name": "Sandbox Customer",
  "customer_number": "08000000001",
  "package_name": "Sandbox Bouquet",
  "invoice_period": 1
}

Hand it back on the order:

Cable TVbash
curl https://stagingapi.getelectric.ng/api/v2/reseller/orders \
  -H 'Authorization: Bearer <your-test-key>' \
  -H 'Content-Type: application/json' \
  -d '{
    "reference": "sandbox-tv-001",
    "service": "cable_tv",
    "provider_id": 12,
    "plan_id": 902,
    "target": "08000000001",
    "lookup": {
      "customer_name": "Sandbox Customer",
      "customer_number": "08000000001",
      "package_name": "Sandbox Bouquet",
      "invoice_period": 1
    }
  }'

Note

Live target verify passes the provider's own payload straight through, so the live shape varies by provider and will carry fields the sandbox does not. Read what you get rather than assuming these four keys are all there is, and pass back only the four that are forwarded.

The webhook gap to plan for

A VAS callback carries no target, provider_id or plan_id. When 08000000004 settles 15 seconds later, the body tells you the service and your reference, and nothing about which number was topped up.

order.settled, for a data orderjson
{
  "event": "order.settled",
  "mode": "test",
  "reference": "sandbox-data-001",
  "state": "delivered",
  "settled": true,
  "service": "data",
  "amount": 1000,
  "message": "Delivered.",
  "settled_at": "2026-11-18T09:35:02+01:00",
  "transaction": "TESTSW-1C4E9A72B5D3608F"
}

So keep your own record, keyed by your reference, of what you sold and to whom. Test it here, where getting it wrong costs nothing.