SOUND.RADAR
API Center
Private developer center for SOUND.RADAR chart intelligence, music discovery, radio monitoring, and commerce data services.
Service Catalog
Production-facing API surfaces
Filter by domain, verify live status, then open the branded guide for usage notes or the health endpoint for a quick operational check.
Spotify Charts
Spotify chart data service for SOUND.RADAR ranking workflows.
Billboard Charts
Billboard chart snapshots, dates, rank history, and latest chart entries.
Melon Charts
Melon realtime, HOT100, daily, and weekly chart snapshots with rank changes.
Bugs Charts
Bugs realtime, daily, and weekly chart snapshots with MySQL-backed history.
Genie Charts
Genie realtime, daily, and weekly Top 200 chart data served as TOP100 APIs.
iTunes Digital
Country-level iTunes chart data backed by VPS collection and MySQL.
YouTube Charts
YouTube video and shorts chart bundles for global and country views.
X Trends
X trending topics by WOEID with MySQL snapshots and location-based lookups.
Amazon Music
Amazon Music chart service for music ranking and catalog signals.
Amazon Digital
Digital music best-seller snapshots imported from VPS collection runs.
Amazon CD & Vinyl
Physical music best-seller rankings, product history, and snapshots.
iHeartRadio
Radio station directory, current plays, and monitored track history.
Status Matrix
Public routes and operational ownership
These are the stable public paths used by integrations. Internal ports are kept here for operators only and should not be called directly.
Engineering Standards
A predictable contract for partner and product integrations.
Each service keeps a branded guide, an original Swagger surface, and a health check. The public domain is the contract; backing ports and collectors are operational details.
Availability first
Health and OpenAPI links are public service checks. A Live badge means the reverse proxy and backing application are reachable from the public domain.
Guide before schema
Use the branded guide for implementation context, then open Swagger when exact request models or interactive testing are needed.
Credential discipline
Protected endpoints should be called with the issued API key header. Keep keys outside client-side code and rotate them when a partner integration changes.
Request Pattern
Clean public paths, private backing ports.
Public integrations should use https://api.soundradar.co with the
short service paths below. Legacy -api paths remain available only
for compatibility.
https://api.soundradar.co
/spotify/docs or /youtube/docs.
Operations
Release and maintenance notes
Short public paths enabled
Moved public examples to clean service roots like /spotify, /billboard, /youtube, and /radio.
api.soundradar.co mapped
Separated the API center onto the SoundRadar API domain with SSL, status checks, and branded guides.
Compatibility routes retained
Kept legacy -api paths online while publishing shorter integration URLs for new partners.
Reference
Common integration examples
Health check
curl https://api.soundradar.co/billboard/health
OpenAPI schema
curl https://api.soundradar.co/spotify/openapi.json
Protected request
curl -H "X-API-Key: $SOUND_RADAR_API_KEY" \
https://api.soundradar.co/youtube/charts