MNTN

MNTN (formerly SteelHouse) is a Connected TV and Performance TV advertising platform. Its reporting API (version 3.0) exposes campaign, creative, and placement performance data — including spend, impressions, and clicks — so you can export MNTN reporting outside the platform UI. Nexla connects to the MNTN Reporting API to ingest this data for analysis, reporting, and downstream integration.

Power end-to-end data operations for your MNTN API with Nexla. Our bi-directional MNTN connector is purpose-built for MNTN, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to MNTN or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your MNTN workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

Before creating an MNTN credential, you need your MNTN reporting API key. MNTN uses a single API key to authenticate all reporting requests; the key is sent as a URL parameter and grants access to all reporting data for the account it belongs to.

To obtain your API key, follow these steps:

1. Sign in to your MNTN account.

2. Select My Account from the account dropdown menu in the top-right corner.

3. In the left navigation pane, choose API under the MY ACCOUNT section.

4. Click the Copy button to copy your API key.

All MNTN users on your account can access this key. Treat it like a password and only share it with platforms you trust to access your reporting data. If the key is compromised, contact MNTN to have it rotated.

For more information, see the MNTN API documentation and Access your API key.

Authenticate

Credentials required

Field	Required	Secret	Description
API Key	Yes	Yes	Your MNTN reporting API key, from My Account > API in the MNTN platform. Grants access to all account reporting data for the account it belongs to.

Create a credential in Nexla

1. After selecting the data source type, click the Add Credential tile to open the Add New Credential overlay.

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

3. Enter your MNTN reporting API key in the API Key field. This is the key you copied from My Account > API in the MNTN platform, as described in Prerequisites. The API key authenticates all reporting requests and is sent as a URL parameter to the MNTN Reporting API.

4. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source creation.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the MNTN connector tile, then select the credential that will be used to connect to MNTN, and click Next; or, create a new MNTN credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common MNTN reporting endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

Most reporting endpoints accept a Begin Date and an optional End Date. The begin date can be a fixed date in YYYY-MM-DD format or a relative token such as mtd (month-to-date) or wtd (week-to-date). Omit the end date to use MNTN's default end-of-range behavior for the chosen begin token.

[Rest API] Campaign Performance

Daily campaign-level performance: campaign id/name by day, with spend. Mirrors MNTN's 'Campaign ID/Name x Daily Spend' reference report.

• Set the Begin Date (required) to a date in YYYY-MM-DD format or a relative token such as mtd or wtd, and optionally set the End Date to bound the report range.
• Returns campaign id and name broken down by day, along with spend, impressions, and clicks.

For details on the reporting dimensions and metrics available in MNTN reports, see the Reference: Common API requests documentation.

[Rest API] Creative Performance

Daily creative-level performance: campaign + creative id/name by day, with spend. Mirrors MNTN's 'Campaign Name & Creative ID x Daily Spend' reference report.

• Set the Begin Date (required) to a date in YYYY-MM-DD format or a relative token such as mtd or wtd, and optionally set the End Date to bound the report range.
• Returns campaign and creative id/name broken down by day, along with spend, impressions, and clicks.

For details on the reporting dimensions and metrics available in MNTN reports, see the Reference: Common API requests documentation.

[Rest API] Placement Performance

Daily publisher/network-level performance (inventory delivery breakdown) with spend/delivery metrics, via the confirmed real PublisherInfo/NetworkInfo dimensions.

• Set the Begin Date (required) to a date in YYYY-MM-DD format or a relative token such as mtd or wtd, and optionally set the End Date to bound the report range.
• Returns publisher and network id/name broken down by day, along with spend, impressions, and clicks.

For details on the reporting dimensions and metrics available in MNTN reports, see the Reference: Common API requests documentation.

[Rest API] Account Spend Summary

Account-level daily spend and delivery summary across all campaigns.

• Set the Begin Date (required) to a date in YYYY-MM-DD format or a relative token such as mtd or wtd, and optionally set the End Date to bound the report range.
• Returns a daily spend and delivery summary aggregated across all campaigns in the account.

For details on the reporting dimensions and metrics available in MNTN reports, see the Reference: Common API requests documentation.

[Rest API] Metrics Catalog

List all available reporting dimensions and metrics (the 'legend') that can be used in the data/sum parameters of the performance reports.

• This endpoint takes no parameters. It returns the full catalog of dimensions and metrics available for use in MNTN reporting requests.

Use this endpoint to discover the valid dimensions and metrics before building custom reports. For more information, see the Upgrade to API 3.0 documentation.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

MNTN data sources can also be manually configured to ingest data from any valid MNTN Reporting API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new MNTN data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.