Skip to main content
GET
/
requeryTransaction
/
{orderId}
curl --location 'https://api.bleeprs.com/api/requeryTransaction/bpr_req_a1b2c3d4e5f6' \
--header 'Authorization: Bearer YOUR_API_KEY'

{
  "gatewayStatus": "00",
  "gatewayMessage": "Successfully Processed",
  "requestReference": "bpr_req_a1b2c3d4e5f6",
  "data": {
    "status": "SUCCESS",
    "reference": "bpr_req_a1b2c3d4e5f6",
    "token": "1234 5678 9101 1121 3141",
    "units": 24.5
  }
}

​
Overview

Customers can requery vending transactions from the public API. Use this endpoint when an airtime, data, electricity, or cable TV purchase returns a pending response. The orderId path value is the requestReference returned by the original purchase request.

​
Request

curl --location 'https://api.bleeprs.com/api/requeryTransaction/bpr_req_a1b2c3d4e5f6' \
--header 'Authorization: Bearer YOUR_API_KEY'

​
Path Parameters

​
Response Fields

​
gatewayStatus
string
"00" indicates the requery request was processed successfully.
​
gatewayMessage
string
Human-readable requery result message.
​
requestReference
string
Unique reference for the requery request.
​
data
object
Current transaction details.
​
status
string
Current transaction status, such as SUCCESS, FAILED, or PENDING.
​
reference
string
Transaction reference being checked.
​
token
string
Electricity token for successful prepaid electricity purchases, when available.
​
units
number
Electricity units for successful electricity purchases, when available.

​
Status Codes

CodeMeaning
200Requery completed. Use data.status to determine the final outcome (SUCCESS, FAILED, or still PENDING).
404No transaction was found for the supplied orderId. Double-check the requestReference from the original purchase response.
425Too early. Requery is only available at least 2 minutes and 1 second after the original purchase.
429The maximum number of requery attempts for this transaction has been reached. Contact support to have the status resolved manually.
502The provider could not be reached to confirm the status. Retry after a short delay.

​
Notes

  • Use the requestReference from the original purchase response as orderId.
  • Wait at least 2 minutes after the original purchase before requerying a pending transaction.
  • Store both the original purchase response and the requery result for reconciliation and support.
  • For successful electricity purchases, the response can include token and units details.
  • If the transaction is still PENDING, do not submit a duplicate purchase for the same customer request.
  • In the Mintlify playground, the orderId value you type is preserved as you move between endpoints — paste the requestReference from a real purchase response to test end-to-end.

Authorizations

​
Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

​
orderId
string
required

The requestReference returned by the original purchase response. The value you type here is preserved across the playground — paste your real reference to test against a live transaction.

Response

Requery completed. Use data.status to determine the final outcome.

​
gatewayStatus
string
Example:

"00"

​
gatewayMessage
string
Example:

"Successfully Processed"

​
requestReference
string
Example:

"bpr_req_a1b2c3d4e5f6"

​
data
object