Engineering & Developers
Get to air. Build on your station.
Wire your station from the cloud to the transmitter, put now playing on your website, sync your library and logs with other systems, or let an AI assistant run errands in your stations. Your data is yours.
Cloud to transmitter
Every way to get the station from the cloud to your AM, FM or HD Radio transmitter, and how to keep it on air.
OpenREST API
Read, create, change and delete almost anything: logs, the library and its audio, scheduling, traffic, sales, listeners, contests and more.
OpenMCP server
Connect Claude, Cursor, VS Code or another MCP client to ask about your stations, or have it do the work, in plain English.
OpenSDKs
Official clients for JavaScript/TypeScript and Python, with retries, paging, safe edits, audio uploads and webhook checks built in.
OpenFeeds & embeds
No key needed: the embeddable player, the listener page JSON, the radio display feed and podcast RSS.
OpenChangelog
Every new feature, improvement and bug fix, as it ships.
OpenQuick start
Your first request in a minute.
- 1Make a keyIn the app, open Organization › API keys › New API key, pick whose access it uses and what it can do. AI assistants can simply sign in instead.
- 2Copy itThe key is shown once. Keep it on your server, never in a web page.
- 3Call the APISend it in the X-API-Key header. Each key can make 120 requests a minute.
Your rules, enforced
Every key and sign-in works as one person, with the same checks as the app. Read-only keys never change anything.
Permission by permission
Each key gets only the permissions and stations you pick. Revoke it any time.
One API, two ways in
The REST API and the MCP server run the same operations with the same checks.
Have something to build?
Tell us what you'd like the API to do next. We add endpoints our customers ask for.


