Transitioning to HLS
We’re moving our streaming infrastructure to HTTP Live Streaming (HLS) with Fragmented MP4 as the container format. This approach ensures compatibility across all codecs, including lossless. It also adapts automatically to each listener’s bandwidth and device capabilities — resulting in smoother playback, fewer dropouts, and a consistent experience everywhere.
➡️ Learn more about HLS here.
HLS Streams
Your application should select the appropriate stream based on user bandwidth.
The available streams are segmented as follows:
Codec | Profile | Bitrate (kbps) |
---|---|---|
FLAC* | fLaC | 14410 |
AAC | mp4a.40.2 | 320 |
AAC | mp4a.40.2 | 128 |
HE-AACv1 | mp4a.40.5 | 64 |
HE-AACv2 | mp4a.40.29 | 32 |
* Requires authorization
Authorization
Authorization via query parameters has been deprecated.
To continue accessing lossless streams, use the Authorization
header instead.
➡️ Learn how to obtain tokens here.
Synchronization
We recommend using EXT-X-PROGRAM-DATE-TIME
to synchronize playback with our API. More details are available here.
API Endpoints
Our API now publishes updated streaming endpoints while retaining the existing structure for backward compatibility:
{
"streams": {
"progressive": "https://listen.atomic.radio/hitradar",
"hls": "https://listen.atomic.radio/hitradar.m3u8"
}
}
{
"streams": {
"progressive": "https://listen.atomic.radio/hitradar",
"hls": "https://listen.atomic.radio/hitradar.m3u8"
}
}
Progressive HTTP Streaming
- Multiple mounts for different bitrates (e.g.,
/hitradar/highquality
,/hitradar/lowquality
) are no longer needed. - All progressive traffic will redirect to MP3 320kbps.