Purpose of the REST Report API
The etracker REST Report API v3 is an interface you can use to develop your own applications using the etracker data or to further process this data at your company.
Access to the REST Report API
In order to be able to use the etracker REST Report API, you need to register with etracker. Save a valid email address with our Support in order to receive a so-called developer token. Using your email address and the developer token, you will then be authorised to access etracker data using the etracker REST Report API.
In order to protect your privacy and prevent unauthorised use of the etracker Web Services API, you should keep the developer token confidential.
Using your valid email address, you can be kept informed about further developments and changes to the etracker REST Report API in realtime. When registering, you can indicate if you would like to receive regular information on the etracker API or not.
The email address and the developer token are to be supplied in each Web Service Request within the query header.
If you have the etracker Analytics Enterprise Edition, you can use the REST Report API for free. In all other cases, you can book the REST Report API for an extra charge. We are happy to provide you with prices on request. If necessary, contact your etracker consultant or Support.
Using the REST Report API
To simplify using the etracker REST Report API, you should create a REST client. The structure of the client depends on the programming language used. The client sends the queries to the service and returns defined values which can then be further processed.
Apart from the development environment for the programming language used, you will not need any additional software or installation on your system.
Structure of the URL for the REST Calls
The etracker REST API only accepts calls via https. All of the calls described in this document are GET queries. The address of the etracker REST Server is ws.etracker.com and the basic URI for all queries is /api/rest/v3. The REST calls can be written with or without parameters. REST calls for calling report data without parameters are not recommended as under certain circumstances very large data quantities are returned. The parameters do not differentiate between upper and lower case. Example with parameters for calling data from the report ‘Device’:
The same example without parameters (not recommended):
Each REST Report query must have a header. This is for performing the authentication to the API.
The following header information is mandatory.
- email: This header element includes the email address of the developer who has access to the API.
- developerToken: This header element includes the developer token which you can request from the etracker Support.
- accountId: This element includes the etracker account ID. For authentication purposes, an etracker sub-user can also be entered (format: #accountId#-#subuserId#)
- password: This element includes the password of the etracker account.
X-ETfirstname.lastname@example.org X-ET-developerToken=ab7891ca89d9b4d10dc1703a7f0214256babe6c9 X-ET-accountId=18854 X-ET-password=demo
In Firefox you can also use modify headers (https://addons.mozilla.org/en-us/firefox/addon/modify-headers/) to send on these headers.