Response
5.3 Response
Sample Response
Below is a sample response of a get request, limit=2
. Notice has_next_page
is true
, meaning there are still existing results that need to be requested. You should query again with the after
param to fetch the next page using after=WyIyMDIyLTAyLTI0VDE2OjAwOjI3Ljg1OCswODowMCIsInRyYW5zYWN0aW9uXzFkYWFlZWVkLTAyNTAtNDljOS1iZDNiLWE1ODc5NzhlZGE2OCJd
. And repeat until has_next_page
is false.
Response Format
The response will include data
which is an array of transaction objects.
object
String
Value will be “transaction”.
id
String
Transaction id.
campaign_id
String
Campaign id.
transaction_type
String
Value will be “redeem”.
value
Number
Value of the transaction.
metadata
String
Null
merchant_id
String
Merchant id.
merchant_name
String
Merchant name.
created_at
String (ISO8601)
Datetime transaction was created.
updated_at
String (ISO8601)
Datetime transaction was updated (when assigned a payout)
verifier_id
String
User id that verified the transaction, which will be the API key user for supermarket merchants.
verifier_name
String
User name of the verifier.
bank_statement_id
String
Null
It will also include page_info
which contains the following.
has_next_page
Boolean
Indicator if there is a next page.
has_previous_page
Boolean
Indicator if there is a previous page.
start_cursor
String
Encoded string to indicate the reference starting point of the page. Similar behavior as typical paginated api.
end_cursor
String
Encoded string to indicate the reference ending point of the page. Similar behavior as typical paginated api. Can be supplied into the after query parameter to retrieve the next page.
Last updated