Verification

Verify a target

POSThttps://stagingapi.getelectric.ng/api/v2/reseller/targets/verify

Confirm a cable TV smartcard and read back the customer and their package. Needed for cable TV, where what you pass back as lookup decides the invoice. Airtime and data need no verification.

Shares the budget your orders do not reserve. Works with a live or test key.

Request
curl -X POST 'https://stagingapi.getelectric.ng/api/v2/reseller/targets/verify' \
  -H 'Authorization: Bearer <your-test-key>' \
  -H 'Content-Type: application/json' \
  -d '{
  "provider_id": 12,
  "target": "08000000001"
}'
Body
{
  "provider_id": 12,
  "target": "08000000001"
}
Response
{
  "success": true,
  "status": "success",
  "code": 200,
  "message": "OK",
  "data": {
    "customer_name": "Sandbox Customer",
    "customer_number": "08000000001",
    "package_name": "Sandbox Bouquet",
    "invoice_period": 1
  }
}

Authorization

Authorizationstringheaderrequired

Your reseller API key, as Bearer <key>.

Body

provider_idintegerrequired

From listProviders.

1 or more

targetstringrequired

The smartcard or phone number. In test mode this must be one of the reserved sandbox targets.

At most 64 characters

Response 200

The target and its customer. Live mode passes the provider's payload through unchanged; test mode returns a fixed sandbox customer.

successbooleanrequired
statusstringrequired

One of success, failed

codeintegerrequired

The HTTP status, repeated in the body. It is not an error code: this API has none, so the message text is the only thing distinguishing one refusal from another, and message text is not a stable contract.

messagestringrequired
dataobjectrequired

In live mode the provider's own payload, unchanged. Pass the parts you need back as the order's lookup object.

Show child attributes
customer_namestring
customer_numberstring
package_namestring
invoice_periodinteger

Other responses

401
No key, a malformed Authorization header, or a key that no longer exists.
403
The key is real but may not do this. Three separate causes, and only the message tells them apart: the token cannot use the reseller API at all, the calling address is not on your allowlist, or the key carries both test and live access and must be reissued for one mode.
422
The request was refused. message says what is wrong, in English; there is no machine-readable code to branch on.
429
You have too many requests open at once. This is a concurrency cap, not a rate limit: wait for your open requests to finish rather than backing off a fixed time. Retry-After is 1.
503
We could not reach the provider. Safe to retry, and for an order you must retry with the same reference.