SOUND.RADAR API DEV
NOINDEX Docs

SOUND.RADAR

API Center

Private developer center for SOUND.RADAR chart intelligence, music discovery, radio monitoring, and commerce data services.

Checking services online
Status refresh pending
Services 12 public root paths
Domains 3 charts, radio, commerce
Docs 13 center index + service guides
Access Keyed protected data endpoints

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.

S Checking

Spotify Charts

Spotify chart data service for SOUND.RADAR ranking workflows.

/spotify Port 8001
B Checking

Billboard Charts

Billboard chart snapshots, dates, rank history, and latest chart entries.

/billboard Port 8040
M Checking

Melon Charts

Melon realtime, HOT100, daily, and weekly chart snapshots with rank changes.

/korea-chart Port 8050
B Checking

Bugs Charts

Bugs realtime, daily, and weekly chart snapshots with MySQL-backed history.

/korea-chart Port 8050
G Checking

Genie Charts

Genie realtime, daily, and weekly Top 200 chart data served as TOP100 APIs.

/korea-chart Port 8050
I Checking

iTunes Digital

Country-level iTunes chart data backed by VPS collection and MySQL.

/itunes-digital Port 8020
Y Checking

YouTube Charts

YouTube video and shorts chart bundles for global and country views.

/youtube Port 8030
X Checking

X Trends

X trending topics by WOEID with MySQL snapshots and location-based lookups.

/x-trends Port 8060
A Checking

Amazon Music

Amazon Music chart service for music ranking and catalog signals.

/amazon Port 8002
D Checking

Amazon Digital

Digital music best-seller snapshots imported from VPS collection runs.

/amazon-digital Port 8010
V Checking

Amazon CD & Vinyl

Physical music best-seller rankings, product history, and snapshots.

/amazon-cd Port 8004
R Checking

iHeartRadio

Radio station directory, current plays, and monitored track history.

/radio Port 8000

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.

Service Public path Domain Port Guide
Spotify Charts/spotifyCharts8001Guide
Billboard Charts/billboardCharts8040Guide
Melon Charts/korea-chart/melonCharts8050Guide
Bugs Charts/korea-chart/bugsCharts8050Guide
Genie Charts/korea-chart/genieCharts8050Guide
iTunes Digital/itunes-digitalCharts8020Guide
YouTube Charts/youtubeCharts8030Guide
X Trends/x-trendsCharts8060Guide
Amazon Music/amazonCommerce8002Guide
Amazon Digital/amazon-digitalCommerce8010Guide
Amazon CD & Vinyl/amazon-cdCommerce8004Guide
iHeartRadio/radioRadio8000Guide

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.

01

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.

02

Guide before schema

Use the branded guide for implementation context, then open Swagger when exact request models or interactive testing are needed.

03

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.

Base URL https://api.soundradar.co
Auth Send issued API keys from server-side integrations only.
Docs Use service docs such as /spotify/docs or /youtube/docs.
Status Cards check the current public paths, not internal ports.

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