Get redemption order status history
POST
/v1/redemption-transactions/transaction-history
What this endpoint does
INFO
Quick start
Authentication and permission
| Send | Permission | Community scope |
|---|---|---|
Authorization: Bearer <apiKey> | readRedemptionTransactions | Community scope is derived from the key; do not send a community identifier. |
Complete examples
{
"transactionId": "ORD202607220001"
}Success and readback
code = REDEMPTION_TRANSACTION_STATUS_HISTORY_RETRIEVED{
"status": "success",
"code": "REDEMPTION_TRANSACTION_STATUS_HISTORY_RETRIEVED",
"message": "Get redemption order status history successfully",
"data": {
"transactionId": "ORD202607220001",
"changes": [
{
"oldStatus": "new_purchase",
"oldStatusName": "New Purchase",
"newStatus": "refunded",
"newStatusName": "Refunded",
"remark": "Refunded by API hardening proof",
"updatedAt": "2026-07-22T02:10:00.000Z"
}
]
}
}CHECK
Errors and recovery
code, never message text.| HTTP | Machine code | What the caller should do | Retry? |
|---|---|---|---|
| 400 | VALIDATION_FAILED | Use a valid public ORD identifier. | No, fix first |
| 401 | AUTHENTICATION_REQUIRED | Add the Authorization header. | No, fix first |
| 401 | AUTHENTICATION_FAILED | Authentication could not be completed. | Retry once |
| 403 | API_KEY_PERMISSION_DENIED | Request the readRedemptionTransactions permission; no resource data is returned. | No, fix first |
| 404 | REDEMPTION_TRANSACTION_NOT_FOUND | Refresh the order list. | After refreshing the ID |
| 500 | INTERNAL_ERROR | Retry with exponential backoff and the same request context, then escalate. | Yes, with backoff |
Retry safety
TIP
Gotchas
Next steps
Request
Body Params multipart/form-dataRequired
Responses
Request Request Example
Shell
JavaScript
Java
Swift
curl --location 'https://api.returning.ai/v1/redemption-transactions/transaction-history' \
--form 'transactionId=""'Response Response Example
200 - Example 1
{}Modified at 2026-08-08 01:52:15