Supported API Features
Which parts of the AzuraCast API Auvyra uses.
Verified against the AzuraCast OpenAPI specification, version 0.24.0, and tested against AzuraCast's public demo server.
| Feature | Endpoint | Needs a key | Status |
|---|---|---|---|
| Server status | /api/status | No | Available |
| Station list | /api/stations | No | Available |
| Station details | /api/station/{id} | No | Available |
| Now playing | /api/nowplaying/{id} | No | Available |
| API key check | /api/frontend/account/me | Yes | Available |
| Song history | /api/station/{id}/history | Yes | Available |
| Service status | /api/station/{id}/status | Yes | Available |
| Skip, disconnect, restart | /api/station/{id}/backend/{action}, /api/station/{id}/restart | Yes | Available |
| Queue | /api/station/{id}/queue | Yes | Available |
| Playlists | /api/station/{id}/playlists, /api/station/{id}/playlist/{playlistId}/toggle | Yes | Available |
| Moderating song requests | /api/station/{id}/reports/requests | Yes | Available |
| Public song requests | /api/station/{id}/requests, /api/station/{id}/request/{requestId} | No | Available |
| Podcasts | /api/station/{id}/public/podcasts, /api/station/{id}/public/podcast/{podcastId}/episodes | No | Available |
Listener counts, live DJ details, the next track and stream information are part of the now-playing and station data.
The features from service status down depend on your API key's permissions. If your key is not allowed to use one, the page says so.
Rate limits
AzuraCast can answer with HTTP 429 when it receives too many requests. Auvyra reports this plainly and caches now-playing data to keep its request rate low.
Planned
Auvyra sends API keys using both the Authorization: Bearer and X-API-Key headers, which AzuraCast documents.