TIDAL · Arazzo Workflow
TIDAL Track Playback Manifest
Version 1.0.0
Resolve a track by ISRC, confirm it, then fetch its playback manifest.
Provider
Workflows
track-playback-manifest
Find a track by ISRC and fetch its playback manifest.
Filters the tracks collection by ISRC, confirms the first match, and requests an HLS playback manifest for it.
1
findByIsrc
{$sourceDescriptions.catalogApi.url}#/paths/~1tracks/get
Look up tracks matching the supplied ISRC using the tracks collection filter, returning candidate track resources.
2
getTrack
{$sourceDescriptions.catalogApi.url}#/paths/~1tracks~1{id}/get
Read the matched track in full to confirm it before requesting a playback manifest.
3
getManifest
{$sourceDescriptions.playbackApi.url}#/paths/~1trackManifests~1{id}/get
Request an adaptive HLS playback manifest for the confirmed track, supplying the required manifestType, formats, uriScheme, usage, and adaptive parameters.
Source API Descriptions
openapi
Arazzo Workflow Specification
Work with this as data
Every workflow here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for arazzo workflows
4 MCP tools reach this
find_arazzoBrowse and filter every workflow in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This workflow
curl "https://apis.io/api/v1/arazzo/tidal-track-playback-manifest-workflow"
All arazzo workflows
curl "https://apis.io/api/v1/arazzo?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.