Current track data
Display live artist and title information from a compatible station endpoint.
Connect current artist, track title, artwork, show information and recent-played data to websites, mobile apps, players, Discord tools or custom broadcast dashboards.
Display live artist and title information from a compatible station endpoint.
Use album or station artwork where the source API provides suitable images.
Feed now-playing information into custom PHP or JavaScript components.
Reuse current-track data inside Android, iOS or PWA applications.
Send selected station information to Discord or other supported services.
Extend current-song data into a recently-played list when the source includes history.
Now-playing metadata is the information that describes what a station is broadcasting at the current moment. At minimum this may include artist and track title. Richer platforms can also provide album artwork, elapsed time, listener counts, presenter details and recent song history. A metadata integration collects that information from the streaming platform and presents it in a listener-friendly format.
AzuraCast exposes structured station data that is well suited to websites and applications. A custom integration can poll or request the station endpoint, extract the current song and related values, then update a player, website card, mobile app or other service. The exact fields available depend on the station configuration.
Other radio panels can provide now-playing information through APIs, status pages or compatible endpoints. The integration approach should be chosen after reviewing the actual data returned by the station. It is better to build around the real endpoint than assume every hosting panel exposes identical fields.
Current-track data can be reused beyond the website. A station may want a Discord bot, community dashboard, digital signage screen or studio monitor to show what is playing. A lightweight API layer can normalise the data and provide a consistent output for these tools.
Metadata should be refreshed frequently enough to feel live without placing unnecessary load on the station panel. Caching, timeouts and graceful fallbacks help keep the listener interface stable when the upstream API is briefly unavailable.
Show artist and title directly beside playback controls.
Explore player →Turn metadata history into a recently-played list.
Explore history →Create live station pages powered by API data.
Explore websites →Reuse the same now-playing source in a branded app.
Explore apps →Yes. AzuraCast provides structured APIs that can be used for current-track and station information.
Yes, selected now-playing data can be formatted for a compatible bot or webhook-based integration.
The refresh interval depends on the source API and use case. It should be frequent enough to reflect song changes without creating excessive requests.
Yes, when the source provides a usable artwork URL or an additional lookup service is configured.
A well-built integration should fail gracefully, use short-term caching where appropriate and avoid breaking the entire player or page.
Send the station panel, public API endpoint and the website, app or community service you want to update.