Skip to main content

Crate tidal_player_api

Crate tidal_player_api 

Source
Expand description

Tidal HTTP API client. See docs/specs/0001-architecture.md.

Base URLs are always injected by the caller. The production URLs are named constants in auth (spec 0002); authenticated requests go through auth::Authenticator.

Modules§

auth
Tidal authentication. See docs/specs/0002-auth.md.
library
The library: lists, pages and writes (spec 0006). Requests are answered through the Authenticator; every list and page has a pure DTO to core mapping behind it.
metadata
Track metadata and suggestions (spec 0004 “Filling the queue”, “Autoplay”): single tracks, album and playlist contents, track radio.
stream
Stream resolution (spec 0003, AC1–AC5): turns a track ID into a StreamPlan the player can fetch, through GET /tracks/{id}/playbackinfopostpaywall.

Structs§

ApiResponse
A response from auth::Authenticator::get and its siblings: the status, the headers and the whole body, as the server sent them.
Client
HTTP client bound to an injectable base URL.

Enums§

ApiError
Errors returned by Client.

Constants§

SUB_STATUS_NOT_AVAILABLE
Tidal’s subStatus for “Asset is not ready for playback”: a 401 that says the track (or quality) is not available to the account, not that the token is bad (spec 0002 AC18).