Support Home > Analytics, Reports & API > API v1.3 – Querying API

API v1.3 – Querying API

The Data Access API Integration provides additional reporting tools to supplement those available through the Kochava platform.

The Kochava platform provides extensive tools to track everything from impressions thru post-install events for connected devices. The API reporting method provides advertisers with the programmatic tools to gather performance data on an on-demand or scheduled basis.

For clarity, our support documentation for API v1.3 has been divided into the following sections:

The following document defines the structure and the methods for Querying the API.


Structure for Querying API

Parameter Description Format
api_key The api key linked to the user. string
app_guid The name of the app to report on. string
token The token ID of the report that was returned when the report was created. string
max_tokens Maximum number of requests to return. int

Query Authorized Fields for Grouping

Post Endpoint:

https://reporting.api.kochava.com/v1.3/grouping

 

Response Data:


Query Authorized Fields for Filtering

Post Endpoint:

https://reporting.api.kochava.com/v1.3/filtering

 

Response Data:


Query Authorized Values for Timezones

Post Endpoint:

https://reporting.api.kochava.com/v1.3/timezones

 

Response Data:


Query Report Templates

This call return the list of templates that have been created in the system (and stored in kochava_reports.templates. Each template is returned with the pre-set/default values for all the parameters (traffic, grouping, etc…).

 

Post Endpoint:

https://reporting.api.kochava.com/v1.3/templates

 

Response Data:


Query Columns Templates

By default, the Reporting system will generate report with all columns available (>100 in most cases). This may be too much for most request. Each report is broken up into several parts and for each part, columns can be removed or reordered to fit every users needs.

The call to the API is made for an API Key and app guid. The report can be passed, however if it is not, all report columns will be returned. Each user can have default reports set to their individual preference. The call can limit to a report. This call return the list of “parts” and for each one, the order AND the fields selected and field available. If a call is made for all reports, it will return the reports that have specific default for that API Key/App and the default set-up for the ones without. For example, you may get the specific set-up for Install but get the default for Click and Event

 

Post Endpoint:

https://reporting.api.kochava.com/v1.3/reportcolumns

 

Sample Post Data:

 

Sample Response:


Save/Update Columns Templates

Kochava stores a default selection/ordering of the columns for each type of report. That default is used by the UI AND when a report is submitted to the API with [ “default” ] as column_order segment. Once you have customized a report, you can save the set-up so that set-up will be the default for the next report you are submitting. The default is by API Key AND APP.

The call to the API is made for a API Key and the APP ID, not the guid. It can only be made for 1 report type at the time.

 

Post Endpoint:

https://reporting.api.kochava.com/v1.3/reportcolumns/update

 

Sample Post Data:

 

Sample Response Example:

 
 

Last Modified: Sep 12, 2017 at 8:29 am