MNTN Audience + Events API
MNTN · Performance TV

Audience segments, on the screen.

Create the audiences MNTN targets on Connected TV, then keep them in sync from your own stack with one REST API.

Three calls to a live audience.

Authenticate once, create a segment, then stream identities into it. The moment identities resolve, the segment is addressable on MNTN's Performance TV inventory.

01 — Authenticate

Send your API key

Every call carries a key issued with your connection, as a Bearer token or an access_key query param.

Authorization: Bearer <key>
02 — Create a segment

Name the audience

Open a segment with a name and an optional source. You get back a segment_id to populate.

POST /v2026/audience/segments
03 — Add identities

Fill it, keep it fresh

Add identities to the segment in batches. Add and remove as your audience shifts; MNTN targets the current set.

POST /v2026/audience/segments/{segment_id}/identities

Two resources, one relationship.

The whole API is segments and the identities inside them. Everything else is reading, filtering, and keeping that set current.

Base URL
integrations.ex.mountain.com/v2026
Auth
Bearer key or access_key
Format
JSON over HTTPS
Version
Pinned in the path · v2026

The full reference.

Ten operations · segments, identities, events, pagination, errors.

Open the reference