SOUND.RADAR API DEV
Why SOUND.RADAR
Every chart, one signal.
Fifteen chart, radio, and commerce services — Spotify, Billboard, Melon, FLO, VIBE, TikTok, iHeartRadio, Amazon and more — unified behind a single predictable contract. Health-checked, key-protected, and maintained as one branded data layer for product teams.
Checking
services live now
Live signal
Charts, the moment they move.
One call per chart, the same JSON shape every time. The cards below show each chart's current #1 — resolved through SOUND.RADAR and refreshed continuously, never with a key in the browser.
Spotify · Global
Sample
#1
Golden Hour
Aurora Vale
BBillboard · Hot 100
Sample
#1
Paper Crowns
The Lateral
Melon · Top 100
Sample
#1
새벽
한로
Representative entries shown until live data loads. Same response model across every source.
Coverage
Fifteen services. Three domains. One contract.
Every source has its own quirks. We absorb them so you integrate once. Status badges below are checked live against each public health endpoint.
Charts 11
Spotify
Checking
B
Billboard
Checking
Melon
Checking
Bugs
Checking
Genie
Checking
F
FLO
Checking
V
VIBE
Checking
iTunes Digital
Checking
YouTube
Checking
X
X Trends
Checking
T
TikTok Trending
Checking
Radio 1
iHeartRadio
Checking
Commerce 3
Amazon Music
Checking
Amazon Digital
Checking
Amazon CD & Vinyl
Checking
Engineering standards
Built to a predictable contract.
The public domain is the contract; refresh pipelines and runtime details stay inside the SOUND.RADAR platform.
Availability first
Every service ships with a public health or OpenAPI check. A Live badge means the reverse proxy and backing application are reachable from the public domain.
Guide before schema
Each service keeps a branded guide for implementation context, then an original Swagger surface when exact request models or interactive testing are needed.
Credential discipline
Protected endpoints take an issued API key header. Keys stay out of client-side code and rotate when a partner integration changes.
One contract
Why one signal beats fifteen.
Fifteen sources mean fifteen auth schemes, fifteen response shapes, and changing upstream rules. SOUND.RADAR absorbs all of it and hands your product one consistent contract over stable public paths.
Without
17 auth schemes, 17 payload shapes, breakage every release.
With
One key pattern, one JSON shape, maintained data channels.
Result
Ship a chart feature in an afternoon, not a sprint.
Reliability
Boringly available.
Last 60 days
99.9% uptime
Each bar is one day across all public services. Availability is verified through the same health endpoints shown above.
Same shape everywhere
One contract, three lines.
Health check
curl https://api.soundradar.co/billboard/healthOpenAPI schema
curl https://api.soundradar.co/radio/openapi.jsonProtected request
curl -H "X-API-Key: $SOUND_RADAR_API_KEY" \
https://api.soundradar.co/youtube/charts