Developers
Every room has an API.
Nothing in the platform is behind a private door. The schedule, the log, the library, the loyalty ledger and the compliance file are all reachable over the same API the product uses — scoped to your station.
Core API
REST · station-scoped keysProgramming
Shows, hosts, the weekly grid and the clock. Write a schedule change and the air chain picks it up.
Traffic and billing
Orders, spots, flights and affidavits. Post an order, read proof of play back.
Content library
Audio, video, podcast episodes and imaging, with the same metadata the apps and TV channels read.
Listeners and loyalty
Accounts, points, check-ins and rewards. Points are server-authoritative — the ledger is the source of truth.
Compliance
The public file, EAS logs and the FCC paperwork trail, queryable and exportable.
Events
webhooksNow playing
Fires on every element change from the playout engine — what the dashboards and the dashboards in cars read.
Log and schedule
Spot aired, break completed, show started, schedule amended.
Listener activity
Check-ins, point awards and redemptions, as they happen.
Getting started
Keys and scopes
Keys are issued per station and scoped per surface, so an integration that reads the log cannot touch the loyalty ledger.
Documentation
Endpoint reference, webhook payloads and the data model.
Changelog
Every release, versioned. API changes land here first.