Pull radio airplay data into your own tools

Radio airplay API: every play of your songs, station by station

The WARM API returns every play of your songs that WARM detects on 21,000+ radio stations in 160+ countries: station, country, city, time, duration and ISRC.

Set up with you, by agreement. Your developers can start on real data with a small test allowance.

GET/api/v1/plays?fromDate=20260901&untilDate=20260930
{
  "songName": "Happiness Is So Sad",
  "artistName": "Swedish House Mafia / Lykke Li",
  "isrc": "CBEFB2604917",
  "radioStationName": "Example FM",
  "radioStationId": "123456",
  "country": {
    "name": "Denmark",
    "isoCode2": "DK"
  },
  "city": {
    "name": "Copenhagen",
    "cityId": "2618425"
  },
  "startTime": "2026-09-24 08:14:32",
  "duration": 187
}
One play, as the API returns it. Example values.
21,000+
Radio stations
160+
Countries
Up to 2 years
Of history per song, by agreement
What you get

The data behind the WARM dashboard

The API reads the same detections as your WARM dashboard, so you can build on the numbers your team already uses.

Every detected play

Station, country, city, start time (UTC), duration in seconds, and the song's ISRC.

Grouped totals

Plays counted by song, country, station, date, artist, city or continent, in one call.

CSV reports

The same report your dashboard exports, with each station's audience, for any date range.

Songs and metadata

Search the catalogue, read title, artist, album, label, release date and genre, and add or remove songs.

Who uses it

Built for teams that report on radio every week

One client tracks more than 450 songs through the API.

Radio promoters

Put the plays straight into the reports you send clients, instead of exporting them by hand every week.

WARM for radio promoters

Labels and distributors

Track hundreds of releases and show radio next to streaming in your own dashboards.

WARM for labels and distributors

Music data teams

Join radio plays to your catalogue and other sources by ISRC.

How access works

From first call to first request

  1. Tell us what you need

    How many songs, how much history, and what you are building. A 20-minute call is usually enough.

  2. We set up your account

    You get a song allowance and a history window of up to two years. We can start with a small test allowance so your developers can try it on real data.

  3. Get a token and call the API

    Exchange your login for a bearer token and send it with each request. The endpoints are documented in the API reference.

Quickstart

1. Get a token

Your WARM email and password return a bearer token. Accounts that sign in with Google or Apple have no password; ask us for an API login.

curl -X POST https://public-api.warmmusic.net/api/v1/auth/exchange \
  -H "Content-Type: application/json" \
  -d '{"email":"you@yourlabel.com","password":"YOUR_PASSWORD"}'

2. Read your plays

One row per detection: song, ISRC, station, country, city, start time (UTC) and duration. Filter by date, country, station, artist or song.

curl "https://public-api.warmmusic.net/api/v1/plays?fromDate=20260901&untilDate=20260930&countryCode=DE&pageSize=100" \
  -H "Authorization: Bearer $TOKEN"

Every endpoint, parameter and error code is in the API reference.

Reference

Endpoints, fields and limits

JSON over HTTPS with a bearer token. Every parameter and error code is in the API reference.

Endpoints

Plays and reports

  • GET/api/v1/playsEvery play of your songs, one row per detection, filtered by date, country, city, station, artist or song
  • GET/api/v1/plays/groupedPlay counts grouped by song, country, station, date, artist, city or continent
  • GET/api/v1/reports/csvYour plays as a CSV report, with each station's audience
  • GET/api/v1/reports/csv/linkA short-lived download link for a large CSV report
  • GET/api/v1/analytics/plays-grouped-by-radiostationsPlays per station as CSV

Songs you monitor

  • GET/api/v1/monitorsThe songs you monitor
  • POST/api/v1/monitorsStart monitoring a song from the catalogue
  • POST/api/v1/monitors/upload-and-assign/{agreementId}Upload an MP3 and start monitoring it
  • POST/api/v1/monitors/removeStop monitoring a song
  • GET/api/v1/monitors/archive-searchHow far the history search has got for each song
  • GET/api/v1/agreements/monitorsYour songs and when each one expires

Catalogue and stations

  • GET/api/v1/songs/searchSearch the recording catalogue by title, artist or ISRC
  • GET/api/v1/songs/metadataTitle, artist, album, label, release date and genre of a monitored song
  • GET/api/v1/radio-stationsThe radio stations WARM monitors

Access

  • POST/api/v1/auth/exchangeExchange your WARM email and password for a bearer token

Fields of one play

songName string
Title of the recording
artistName string
Artist or artists
isrc string
ISRC of the recording, for joining to your catalogue
radioStationName string
Station name
radioStationId string
WARM's station id, the same one the station filter takes
country object
Country name and ISO 3166-1 alpha-2 code
city object
City name and id
startTime string
When the play started, UTC, YYYY-MM-DD HH:mm:ss
duration number
Detected length of the play in seconds
monitorId string
Your monitored song the play belongs to

Limits and errors

Authentication
A bearer token from POST /api/v1/auth/exchange, sent as Authorization: Bearer on every call. Login is limited to 20 attempts per address per 10 minutes.
Scope
Plays, reports and monitored songs are always your own account's. History follows your agreement, up to two years.
Errors
JSON with statusCode and message. 401 for a missing or expired token, 403 for a resource your account cannot read, 404 for something not on your account. Back off and retry on 429 and 503.
Paging and dates
Lists take pageNumber and pageSize. Dates are days, YYYYMMDD or YYYY-MM-DD.

Questions teams ask before they start

What is a radio airplay API?

An API that lets your own software read airplay data instead of exporting it by hand. The WARM API returns every detected play of the songs on your account: station, country, city, start time (UTC), duration in seconds and ISRC, plus grouped totals and CSV reports. Access is set up by agreement, with a song allowance and up to two years of history.

Which songs can I get data for?

The songs you monitor on your WARM account. You can add and remove songs through the API or the dashboard, and each song uses one place in your allowance.

How far back does the data go?

Up to two years, depending on your agreement. When you add a song, WARM searches its history for that period.

Are short plays included?

By default the API lists plays of 60 seconds or longer. WARM detects shorter uses too, and the minimum is set per account, so ask us to lower it for yours.

How do I authenticate?

Exchange your WARM account email and password for a bearer token, then send it with every request. API accounts use a password login.

What formats does it return?

JSON from every endpoint, and CSV for reports. Large reports come as a download link.

Can I get data for songs I don't monitor, or for a whole market?

Not through the API today. If that is what you need, tell us on the call and we will tell you what is possible.

What does it cost?

Each agreement is priced by the number of songs and the length of history. Tell us what you need and we will send you a quote.

Tell us what you want to build

We will look at your songs, the history you need and how often you will call, and set up access to match.

Broadcast Monitoring Powered by ACRCloud