GET transactions (by ID)
Advertisers can pull individual transactions, check the status of the transactions, create their reports, and pull additional information that can be shared between publishers and advertisers via clickref (from publisher to advertiser) and orderRef and custom parameters (from advertiser to publisher). In addition to pulling transactions for a certain time frame, transactions can also be pulled by their IDs.
Who can use it
Advertisers
accessToken
advertiser id
access token
ids
show basket products
time zone in short or default format
Further information on query parameters
parameter | format | mandatory/optional |
ids | numeric, comma-separated | mandatory |
timezone | See https://help.awin.com/apidocs/timezones for timezone details. | optional, default is UTC |
showBasketProducts | JSON array | optional |
OK
Note that the field "lapseTime" is the conversion time in seconds
Basket Products
If &showBasketProducts=true then products sent via Product Level Tracking matched to the transaction can be viewed (please see "Conditional data fields" below for restrictions that might apply)
Conditional data fields
Some data fields are available for advertisers depending on additional settings.
| datafield | available for advertisers |
| orderRef | yes |
| clickRef | yes |
| clickRef2 - clickRef6 | no |
| customParameters | yes |
| basketProducts | yes |
| networkFee | yes, if the advertiser has standard invoicing terms |
Response values for "type"
Sale, Lead, Bonus, 2nd Tier, Commission group transaction, PPC, TQS, Mobile Sale, Mobile Lead, Mobile App Install, Mobile App Purchase, Compensation,