The transaction API is used to call the transactions. To do this, the following parameter must be appended to the API call:
For the transaction API there are additional parameters that can be queried. Below is a list of all parameters:
Transaction API filters
ID of the advertiser as integer.
All transactions that are stored under the given advertiser ID within the program.
ID of the project as integer.
All transactions that are stored under the given project ID within the program.
ID of the campaign as integer.
All transactions that are stored under the given campaign ID within the program.
0 = creation date
All transactions that have been created/processed/payed out in a certain period.
Definition of the fields delivered by the transaction api
The columns of downloaded transactions contain the following parameters:
encrypted transaction id
timestamp of the transaction
id of the advertiser within the system
title of the campaign
id of the campaign within the system
id of the project
title of the project
type of transaction – lead, sale, bonus
Payout date - empty if not payed out yet, format: YYYY-MM-DD HH:MM:SS
Processing time - empty if not processed yet, format: YYYY-MM-DD HH:MM:SS
internal salary id, -1 if not payed out yet
Credit note number – document can be downloaded as unter settings =>billing
timestamp of the click - format: YYYY-MM-DD HH:MM:SS
Subid you passed in click / postview - default: NONE
The click referrer if determinable – default: ://NONE
admedia id which led to the transaction
0 = open | 1 = confirmed | 2 = canceled | 3 = paid
cancel reason (if given)
net basked value
internal id of the event
name of the event
in case of basket-tracking, the number of items in the basket, otherwise 0