Overview
The MNTN reporting platform allows you to generate an API request to export data for ingestion into third-party platforms. A standard API request looks like the below links and can be pulled directly from any data table in your Reporting Dashboard. You can customize our API requests by editing and defining the various parameters.
⚠️ Warning: MNTN does not currently support API-based audience data ingestion or direct integrations with some third-party CRM platforms. To upload audience data, use CSV uploads or LiveRamp integration. If you have questions about a specific integration, contact our support team to confirm what’s available.
Pull API Requests
From Templated Reports
The easiest way to create an API Request is to copy the existing link from any data table within your custom reports.
Click Create R2 API Request in the top-right-hand corner of any templated reporting data table.
This will automatically include 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.
From Custom Reports
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 Create R2 API Request in the top-right-hand corner of any custom reporting data table.
A new API Request will be generated. This will automatically include 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.
Customize API Requests
Set the API Key
Your API key is used to access reporting data outside the MNTN reporting platform. You can locate your unique API key in the My Account section of the platform.
Once you've located your API key, you'll input it in the key parameter of the API request.
Set the Begin Date
You can set the date range of the data you want to pull using the Begin Date parameter. Dates should be specified in YYYY-MM-DD format. If you input a hardcoded date, you must specify the End Date.
Alternatively, you can utilize one of the time shortcuts outlined below. Note that all time shortcuts are T-1 and will not provide the current day's data in the final output.
Shortcut | Definition |
D | The current day of data |
Y | The previous day of data |
W | The current week of data beginning with Sunday as the first day of the week |
LastWeek | The prior week of data beginning with Sunday as the first day of the week |
MTD | The current month of data |
LastMonth | The prior month of data |
Thirty | The last 30 days of data |
YTD | The current year of data |
If you are utilizing one of the above time shortcuts, you don't need to specify the End date parameter.
📘 Example: Time shortcut
Set the End Date
The End Date parameter allows you to set the End Date of the date range you'd like to pull. Dates should be specified in YYYY-MM-DD format. If you have hardcoded the Begin Date, you must specify the End date.
📘 Example: End Date
https://api3.mountain.com/apidata?key=123456789&begin=2021-01-30&end=2022-12-31&format=human&data=Advertiser.Impressions,Advertiser.Visits
Set the Format
You can define the format in which you would like your data returned with the Format parameter. The format options are outlined below.
Format | Definition |
CSV | Comma-separated values (downloads to your computer in CSV format) |
Excel | Fully formatted Excel spreadsheet (downloads to your computer in Excel format) |
Human | Human readable format in columns and rows |
JSON | JSON formatted data |
📘 Example: Format
https://api3.mountain.com/apidata?key=123456789&begin=YTD&format=json&data=Advertiser.Impressions,Advertiser.Visits
Define the Data
You can pull in a variety of data metrics from the API request. You can view all available metrics and dimensions using the List Request. Simply input your API key in the key parameter field to view all reporting metrics and descriptions.
The data parameter is formatted as a comma-separated list of Dimension.Metric arguments, outlining the metrics you'd like to view. The API request should contain only metrics from the same dimension to generate a request successfully.
📘 Example: Advertiser dimension
📘 Example: Campaign Group dimension
The CampaignGroup dimension is the preferred format for generating campaign-level reporting.
Use Batch Requests for Large Data Pulls
If a standard API request to /apidata fails due to size or memory constraints, you can submit the same request through the batch endpoint.
The batch endpoint is designed for larger or more complex requests, such as:
Large date ranges
High-cardinality dimensions
Large result sets
Batch Request Endpoint
https://api3.mountain.com/batch?
Use the same parameters you would normally send to /apidata, such as date range, format, requested fields, and API key.
📘 Example:
https://api3.mountain.com/batch?format=human&begin=mtd&data=graph.day,graph.impressions&key=<>
After submitting a batch request, a batch_id is returned. Use that ID to check request status and generate a new download URL when needed.
If your current request runs successfully through /apidata, no changes are needed.
Batch Request Limits
Each advertiser can submit up to 10 batch requests per hour. If an 11th request is submitted within the same hour, the request will fail.
File Availability
Once your batch request is processed:
The download URL remains active for 24 hours
A new download URL can be generated using the
batch_idProcessed files remain available for 10 days
Point-in-Time File Snapshot
Batch files reflect the data available at the time the request is processed.
📘 Example: If a request is processed on Monday at 12:00 PM and the file is downloaded on Tuesday, the file will still contain data only through Monday at 12:00 PM. It will not automatically refresh with newer data.
To retrieve newer data, submit a new batch request.