Status meanings
This page lists what can be supported from the current API behaviour. Where a value is not confirmed, it says so. Where a meaning is unclear, confirm with Spendstream rather than assuming.
Response envelope status
Most endpoints return HTTP 200 and put the real result in the body.
Body | Meaning |
200 | The request succeeded. |
400 | The request was rejected. Read the |
Some responses use a genuine HTTP status instead. For example, getToken can return 401 for an invalid request or signature, and it returns 429 when you exceed five requests per minute.
Transaction statuses
A transaction can change status over time, and you receive a TRANSACTION_UPDATED webhook when it does.
Status | Meaning |
Pending (affiliate) | Reported by the network but not final. It can be adjusted or declined. |
Any other value | Confirm with Spendstream. |
The exact list of transaction status values and which of them are final is to be confirmed with Spendstream. Until you have that list, do not treat a transaction as final on your own assumption.
User statuses
User status values are to be confirmed with Spendstream. A USER_UPDATED webhook is sent when a user changes.
Brand statuses
Brand status values are to be confirmed with Spendstream. Do not hard-code brand availability, because the catalogue changes.
Related pages
- Reconciliation
- FAQ
On this page
- Status meanings