Building on our products
Most products in the group have an API. Each one is separate, with its own keys and its own reference. This page says which products you can build on and where each reference lives.
To connect an AI assistant, browse the MCP library. It lists Workflow product connections, current availability, endpoints, authentication and example connection settings. Radio Workflow's main connection runs through the API Console; the Affiliate Portal has its own station connection. Each entry links to the product's setup guide or reference.
| Product | What you can do | How you authenticate | Reference |
|---|---|---|---|
| Radio Workflow | Work with a station's accounts, contracts, logs, invoices, production and more, on behalf of a Radio Workflow user | OAuth 2.0, with partner credentials from the API Console | console.radioworkflow.com |
| Signal | Read a workspace's business overview and morning briefs, over REST or from an AI assistant | Read-only API keys created inside Signal | Inside Signal |
| Voice Buddy | Everything the product does: speech, cloning, conversion, transcription, dubbing, projects | An API key, which works for both REST and AI-assistant access | Voice Buddy developers |
| Jingle Buddy | Render songs, jingles and station imaging from your own software, on the Station plan and above | An API key | Jingle Buddy developers |
| Meet Buddy | A REST API, plus webhooks and a calendar feed per member | See the reference | Published as an OpenAPI document |
| AR Buddy | Place accounts, pull recovery status and list statements | A bearer token | AR Buddy site |
| RevBuddy | Promotion kits, campaigns, leads, audience, stations, audio and goals over REST or MCP on the Cluster plan | A scoped workspace API key, created by an owner | RevBuddy API reference and MCP connection and setup |
| Table Buddy | Menu, tables, orders, stock and reports; an order placed through the API, once sent, makes the same kitchen ticket and stock movements as one from the POS | An API key scoped to the job | Table Buddy docs |
| Affiliate Portal | Work the network week from a station's own systems: read the order, download the audio, report times and acknowledge changes. Signing a week always needs a person | A station API key created in the portal | Affiliate Portal API reference and MCP guide |
| Talent Buddy | Jobs, scripts and delivery through the HTTP API or MCP; integration release pending | A scoped API key | Talent Buddy API reference and MCP guide |
| Compliance | Station matching and scans, political records, issues/programs, EEO and NCE preparation, deadlines and assigned work over REST or MCP | A scoped, expiring workspace API key created on its Integrations screen, shared by REST and MCP | Compliance OpenAPI contract and MCP connection and setup |
Radio Workflow
The Radio Workflow API uses OAuth 2.0. A user signs in to Radio Workflow and grants your application the scopes it asked for, and your application calls the API with the access token it receives. Your partner key and secret come from the API Console, which also publishes the full API reference and the platform's system status. Keep the secret on your server: never ship it in a browser, a mobile app or a query string.
Radio Workflow users can also connect an AI assistant of their own to their Radio Workflow data, to ask it about their accounts, logs and proposals. The steps are in Radio Workflow's getting-started guides.
Voice Buddy
One key drives both the REST API and AI-assistant access. The reference, code samples, playground and OpenAPI document are all generated from one specification, so they cannot disagree with each other. Webhooks can tell your system when a render has finished. Get an API key.
Jingle Buddy
The full contract is published as OpenAPI. The same billing rules apply as in the product: you pay for seconds of finished audio, the allowance is a ceiling, and there is no overage, so no script of yours can run up a bill overnight.
AR Buddy
Built for station groups and billing software. Everything in the client portal is available over REST, with bearer-token authentication. For example, listing your placed accounts:
curl https://ar.workflowcorp.com/api/v1/accounts \
-H "Authorization: Bearer YOUR_API_KEY"Stations already on Radio Workflow do not need the API to use AR Buddy: they can send accounts from inside Radio Workflow.
Signal
Signal's keys are read-only and belong to one workspace. Create them on Signal's API keys page, where the reference sits beside them.