Overview
Generate an API request from a MNTN reporting table to retrieve its data in your internal systems or third party platforms. The generated request includes the table’s parameters and formatting, along with your account’s API key.
Start with a templated report, build a custom table for additional metrics, or use one of the common requests below.
📝 Note: MNTN doesn't support API-based audience data ingestion or direct integrations with some third-party CRM platforms. To upload audience data, use CRM file uploads or the LiveRamp integration.
Generate Requests From a Reporting Table
Use a templated report
The easiest way to create an API Request is to copy the existing link from any data table within your custom reports.
Click on the Reporting tab.
Click on the Create R2 API Request icon in the top right corner of any templated reporting data table.
This automatically includes all data parameters and formatting from the data table from which it was pulled, as well as the unique API key for your account.
Click Copy and use the API key to export data for ingestion into your internal systems.
Use a custom report
If you'd like to add more metrics than those available on the templated report, you can create a custom data table using our custom report builder.
Click on the Reporting tab.
From the left navigation pane, under My Reports, select the desired custom report.
Click Create R2 API Request in the top right corner of any custom reporting data table.
A new API Request will be generated. This automatically includes all data parameters and formatting from the data table from which it was pulled, as well as the unique API key for your account.
Click Copy and use it to export data for ingestion into your internal systems.
Use Common Reporting Requests
Copy a request below and replace ABCDEFG1234567 with your account’s API key. For instructions on finding your key, see Use Your API Key.
Campaign ID, Campaign Name x Daily Spend:
https://api3.mountain.com/apidata?begin=mtd&format=human&sum=campaigninfo.id&campaigninfo.name&graph.day&data=campaigninfo.id&campaigninfo.name&graph.day&graph.spend&fullname=true&key=ABCDEFG1234567
Campaign Name, Creative ID x Daily Spend:
https://api3.mountain.com/apidata?begin=mtd&format=human&sum=campaigninfo.name&creativeinfo.id&graph.day&data=campaigninfo.name&creativeinfo.id&graph.day&graph.spend&fullname=true&key=ABCDEFG1234567
Campaign Name, Creative Name x Daily Spend:
https://api3.mountain.com/apidata?begin=wtd&format=human&sum=campaigninfo.name&creativeinfo.name&graph.day&data=campaigninfo.name&creativeinfo.name&graph.day&graph.spend&fullname=true&key=ABCDEFG1234567
Campaign ID, Campaign Name, Creative Name x Daily Spend:
https://api3.mountain.com/apidata?begin=mtd&format=human&sum=graph.day&campaigninfo.id&campaigninfo.name&creativeinfo.id&creativeinfo.name&data=graph.day&campaigninfo.id&campaigninfo.name&creativeinfo.id&creativeinfo.name&graph.spend&fullname=true&key=ABCDEFG1234567
Retrieve Larger Reporting Datasets
Use the batch reporting API’s /batch endpoint for requests that need more processing time. It processes requests asynchronously and returns results when they’re ready.
Use batch reporting when:
Your request includes high-cardinality data, such as several columns or data across multiple tables
Your request covers more than four months
Your synchronous reporting request has timed out
You need to backfill historical data or refresh a system daily
The request payload follows the same structure as the synchronous reporting workflow. See the batch reporting API documentation for technical specifications.
Advanced API Reference
Use the MNTN reporting OpenAPI specification to review reporting endpoints, parameters, and response structures.
For most reporting exports, start with a request generated from a reporting table. It includes your account’s API key and the table’s dimensions, metrics, and formatting.
Incompatible Metrics
Not all reporting metrics can be requested together. MNTN prevents incompatible metrics from being combined to avoid misleading or invalid reporting results.
In Reporting, incompatible metrics or attributes are disabled when they cannot be selected with your current configuration.
In API 3.0, you can identify incompatible fields using the exclude-list attribute returned by the /apilist endpoint. Requests that include incompatible metrics will return an error.