Back to Platform Overview
Glossary
APIs
Statistical APIs
Audience APIs

Authorization

To use the Raw Data API, you need to obtain an access token. To do that, using Postman or similar software, send a POST request to the URL: https://dmp-api.admixer.net/Token. Specify the following parameters in the request body

Parameter

Value
username your login
password password to your account
grant_type authorization password
culture “
Note: If the files of the Publisher`s TD are uploaded, the Access Token for Authorization is uploaded using the publisher`s credentials, so in this case, you must specify the ID of the publisher`s Trading Desk in the GET request body. If the Trading Desk ID is not specified, an access error will be displayed.
Nothing changes for Network Trading Desks, and credentials of the TD are specified in the Access Token for Autorization.

You can see how to structure the request for the Publisher`s TD in the screenshot below.

Note that the access token expires after 24 hours.

The request has the following structure:

userName=mylogin@example.com&password=12345&grant_type=password&culture="

Expand the request example
userName=networkUser@example.com&password=mypass12345&grant_type=mypass54321&culture="

In response, you will get a JSON with the access_token field.

Expand an example of the response JSON
{“access_token”=”wTK8HxHDjDYlCdysaee8clQAd2gfVt”}

The value of this response is your authorization token. Specify it for each request in the request header. The header has the following view.

Authorization: Bearer

your_token

Expand an example of the request header in use
Authorization: Bearer wTK8HxHDjDYlCdysaee8clQAd2gfVt

Retrieving data

To get data on audiences, you need to send a GET request to https://dmp-api.admixer.net/dmp/DownloadLog?date= {date}

Expand an example of the data retrieving GET request
https://dmp-api.admixer.net/dmp/DownloadLog?date=2021-04-22

Indicate your authorization token in the request header.

Upon successful authorization, you will receive a file for the selected day with all users in the audience groups in response. In the file you receive, you will see the following data by default.

  • VisKey, Visitor ID, or Admixer UID,
  • RetGroups.Id, audience groups IDs of the user,
  • Event Type (view is set by default for all groups), for audience groups collected in Trading Desks advertising profiles, parameters can be specified (confirmed view, click, video Qs 1-4, etc.). See the table with all events and their IDs at the bottom of this page.
  • Date / Time (in UTC format),
  • IP address,
  • Country, geolocation detected by IP,
  • Device Type (e.g. desktop, smartphone, tablet, TV). See the table with all events and their IDs at the bottom of this page.
  • Platform (OS, Browser),
  • Mobile Device Manufacturer / Brand,
  • RefererUrl, a complete URL or App Bundle of the ad display,
  • Additional parameters that can be retrieved using the RTB protocol when displaying ads on external resources (user geolocation, site, or application category).
Expand the table with all event types and their IDs
ID Event
0 Code (from Tag)
1 View
2 Click
4 ConfirmView
8 FirstQuartile
16 Midpoint
32 ThirdQuartile
64 Complete
128 Request
Expand the table with all device types and their IDs
ID Device Type
0 Unknown
1 MobileTablet
2 PC
3 ConnectedTV
4 Phone
5 Tablet
6 Connected_Device
7 Set_Top_Box
The interval between requests must not be less than 30 seconds
Updated on September 05, 2024