Authenticate against the TIDAL API using OAuth 2.0 client credentials for server-to-server catalog access, then perform a catalog search
domain: developer.tidal.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Register an application in the TIDAL Developer Portal to obtain a client ID and client secret
For app-only (non-user) access, use the client credentials grant against TIDAL's OAuth token endpoint to obtain a bearer access token scoped to your app
Alternatively, for user-context access, use the authorization code flow (init, then initializeLogin to get a login URL, redirect the user, then finalizeLogin) if you're using one of TIDAL's SDKs, or implement the equivalent OAuth 2.0 Authorization Code with PKCE flow directly
Call the TIDAL Web API's search resource (JSON:API-style, served from the openapi.tidal.com v2 surface) with your access token and a query string to search the catalog
Include a `countryCode` parameter on search and catalog requests, since TIDAL catalog availability and results are market-scoped
Re-fetch credentials via the SDK's credentials provider (or refresh the token yourself) before each call rather than caching a token indefinitely, since TIDAL may rotate or upgrade tokens transparently
Known gotchas
Client credentials tokens only grant access to non-personalized, catalog-level resources — user collection/playlist data requires the user-context OAuth flow, not client credentials
The API responses follow the JSON:API spec (data/included/relationships structure), which trips up clients expecting flat REST JSON
TIDAL's developer platform has been actively evolving its endpoint surface; always check the current API reference for which resources (search, playlists, my collection) are GA versus still being unified, since coverage has been expanding incrementally
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?