How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

MNTN Audiences API

Audience and geo-list management.

MNTN Audiences API is one of 17 APIs that MNTN publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Audiences. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, and API documentation.

This API exposes 12 operations across 9 paths, and defines 12 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://api.mountain.com/ptv.

12 operations 9 paths 12 schemas 1 DELETE7 GET1 PATCH3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.mountain.com/ptv
Authentication
HTTP Bearer, API Key, API Key
License
Proprietary
Resource Areas
1

Authentication & Security 3

MNTN Audiences API declares 3 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (Bearer). An API key is passed in the header as X-API-Key (API_Key). An API key is passed in the header as X-API-Key (API Key). By default, every request must be authenticated.

Paths & Operations 12

Across 9 paths, the API surfaces 12 operations — 1 DELETE, 7 GET, 1 PATCH, 3 POST. Each is listed below with its method, path, parameters, and response codes.

audiences 12

Audience and geo-list management.

GET
/api/v1/audiences
List audiences
audiences.list 6 params → 200default
POST
/api/v1/audiences
Create an audience
AudiencesController_create_v1 body → 201default
GET
/api/v1/audiences/campaign/{campaignId}
Get audience by campaign
audiences.getByCampaign 6 params → 200default
GET
/api/v1/audiences/keywords
Search keywords
AudiencesController_searchKeywords_v1 2 params → 200default
GET
/api/v1/audiences/locations
List/Search Geo Locations
audiences.locations.list 6 params → 200default
GET
/api/v1/audiences/{id}
Get an audience
audiences.get 2 params → 200default
PATCH
/api/v1/audiences/{id}
Patch an audience
audiences.patch 1 param body → 200default
POST
/api/v1/audiences/{id}/geo-lists/disassociate
Disassociate geo-lists from an audience
audiences.geoLists.disassociateBulk 1 param body → 200default
DELETE
/api/v1/audiences/{id}/geo-lists/{geoListId}
Disassociate a geo-list from an audience
audiences.geoLists.disassociate 2 params → 204
GET
/api/v1/audiences/geo-lists
List geo-lists
audiences.geoLists.list 3 params → 200default
POST
/api/v1/audiences/geo-lists
Create a geo-list
audiences.geoLists.create body → 201default
GET
/api/v1/audiences/geo-lists/{id}/locations
Get geo-list locations
audiences.getGeoListLocations 3 params → 200default

Schemas 12

The contract defines 12 schemas that model the data the API accepts and returns. The most detailed are CreateAudienceDto (5 properties), CreateGeoListDto (3 properties), PaginatedGeoListsResponseDto_Output (2 properties), UpdateAudienceDto (2 properties). Each schema is shown below with its type and property counts.

GeoListCreatedSingleResponseDto_Output
object
1 property 1 required
DisassociateGeoListsSingleResponseDto_Output
object
1 property 1 required
PaginatedAudiencesResponseDto_Output
object
2 properties 2 required
UpdateAudienceDto
object
Updatable parts of an audience.
2 properties
PaginatedGeoListsResponseDto_Output
object
2 properties 2 required
GeoListLocationsResponseDto_Output
object
1 property 1 required
DisassociateGeoListsDto
object
Geo-list ids to disassociate from an audience.
1 property 1 required
KeywordsSearchResponseDto_Output
object
1 property 1 required
CreateAudienceDto
object
Inputs for creating a new audience.
5 properties 2 required
PaginatedLocationsResponseDto_Output
object
2 properties 2 required
AudienceSingleResponseDto_Output
object
1 property 1 required
CreateGeoListDto
object
Advertiser context, geo-list name, and one or more geo selectors to resolve into location IDs.
3 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

mntn-audiences-api-openapi.yml Raw ↑

Other APIs MNTN publishes across the network.

MNTN Reporting API 3.0
MNTN Advertisers API
MNTN API
MNTN Attribution API
MNTN Batch API
MNTN Campaigns API
MNTN Creatives API
MNTN Flights API
MNTN Organizations API
MNTN Pixel API
MNTN Pmp Campaign Deals API
MNTN Pmp Channels API
Where this information came from

This is an independent, third-party profile of MNTN Audiences API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.