Re-query

When you already have the reference_id from a previous verification, use re-query to retrieve the record again. No unit is debited.

POST/verify-nin/requery

Request

Field	Type	Required	Notes
`reference_id`	string	✅	The `REF-XXXXXXXXXXXX` returned by an earlier verification

curl
Python

curl -X POST https://api.randaverify.com/verify-nin/requery \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"reference_id": "REF-1A2B3C4D5E6F"}'

resp = requests.post(
    "https://api.randaverify.com/verify-nin/requery",
    headers={"Authorization": f"Bearer {token}"},
    json={"reference_id": "REF-1A2B3C4D5E6F"},
    timeout=30,
)

Response (200)

{
  "status": "success",
  "message": "Record retrieved successfully",
  "data": { /* same shape as the original verification */ }
}

Lookup behaviour

The endpoint resolves the reference_id in this order:

Your org’s transaction history in our database (fast path).
Your org’s activity log as a fallback.
NIMC’s upstream re-query endpoint if the record was not found locally.

If step 3 fires, we still do not charge your wallet — the call is treated as a retrieval, not a new verification.

Failure modes

Status	When	Recover by
`404`	The `reference_id` does not match any record on your org or at NIMC	Confirm the ID was typed correctly. References are case-sensitive.
`500`	Both local and upstream lookups failed unexpectedly	Retry, then contact support with the `reference_id`.