The Broadcastify Live Audio Catalog API allows software applications to query Broadcastify's catalog of live audio feeds and access feed metadata, geographic lookups, archive listings, and feed problem reporting. It is one of four Broadcastify APIs (Live Audio Catalog, Calls Client, Calls Ingest / Upload, and Feed Owner), all covered in this Developers section.

We are incredibly developer-friendly. Broadcastify has been built on top of a developer ecosystem since day one, and we want third-party applications that genuinely extend what listeners and broadcasters can do to thrive.

Scope: Live Audio Catalog only

This API covers the live audio feed catalog only (feed metadata, search, geographic lookups, archive listings, problem reports). It does not stream live audio, deliver archive audio files, expose Broadcastify Calls, or expose feed-owner administration. Those are covered by separate APIs in this same Developers section.

What the API is for

The Live Audio Catalog API exists so that radio-related tools and listener-facing utilities can integrate Broadcastify's catalog into their workflow

What the API is not for

We are currently seeing unprecedented demand for API access driven by AI-assisted developers ("vibe-coding") who are using LLMs to spin up applications, sites, and mobile apps that effectively recreate the functionality of Broadcastify itself. We are not licensing any new "police scanner" style mobile applications, free or paid, hobby or commercial, that wrap our live audio catalog into a competing listening experience. The Broadcastify website and the Broadcastify mobile experience are the front doors to this catalog. We will not approve developer access for projects whose purpose is to build a parallel front door on top of our data and infrastructure.

Likewise, applications designed to redistribute, mirror, scrape, or resell Broadcastify content, metadata, or audio, in any form, are not candidates for a developer key.

Commercial and licensed use

Almost every non-personal use case (commercial listening apps, white-label data products, monitoring and alerting services for organizations, training data and AI/ML pipelines, journalism and analytics platforms, situational awareness products) is a commercial use of our products and services and requires a formal license agreement.

All Broadcastify commercial licenses are royalty-based or monthly-fee-based, depending on use case, and governed by a written license agreement covering the specific use case, redistribution rights, attribution, and audit terms. Licensed API access is issued against a signed agreement, so if your project is commercial, the license is the path forward, not a free developer key.

AI and machine-learning use cases are available under license, and we are ready to partner with serious partners on them. Exploratory or "let me try it out and see what I can build" requests, including personal AI projects and early-stage startup experimentation, are treated as commercial use. We are simply not scaled to underwrite open-ended experimentation against our catalog while people figure out whether they want to turn it into a business. We require a defined use case before we can engage. Be ready to partner, and we will be ready to partner with you.

Requesting access

To apply for a developer key or to start a licensing conversation, please write to support@broadcastify.com. Be specific. Helpful detail includes:

• Exactly what the application does, what users it is for, and how each user reaches it
• What Broadcastify data the application needs and why it cannot be served by the public site or mobile app
• Whether it integrates with a radio, scanner programmer, codeplug editor, or other radio-related hardware/software
• For commercial use: company name, projected user count, business model, and the commercial terms you have in mind
• For AI/ML use: training versus inference, dataset retention policy, model distribution, and projected query volume

Requests that boil down to "because I want to," or that read as a pasted LLM prompt with no specific use case, will be declined. We will always tell you why and, where appropriate, point you toward either a better-scoped request or the licensing path. We are happy to support developers who are extending what listeners and broadcasters can do, and we are open to commercial conversations for everything else.