TIDAL Connect controller integration — path for a Control4 driver partner? (client oFk5Bq27TJa3Ik9y) #353
Unanswered
Murraymint1981
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hello TIDAL team,
I'm Ben Murray, founder of BKM Solutions, a UK home-automation company developing integration drivers for the Control4 platform (product line: Botive). I'd like to understand the certification path for a TIDAL Connect controller integration.
We want TIDAL subscribers to browse their own TIDAL library from within Control4 — on wall touchscreens, remotes and the Control4 app — and start playback on the TIDAL Connect-capable speakers they already own, with TIDAL's service driving the device. A certified controller, in the same category as Control4/Snap One, who I believe are already a partner. We are not proposing to build a player or to decode/redistribute audio — playback stays on the customer's own certified hardware, authenticated with their own TIDAL account via OAuth. We act only as a remote control.
I've registered a developer app (client oFk5Bq27TJa3Ik9y, "BKM Native Controller") and validated what's open to us: OAuth 2.0 PKCE, user profile, playlists, search and catalogue browse all work. The gap is playback — the relevant endpoints return 401 subStatus 6004 "Client does not have required access tier" and 403 subStatus 4034 "No content matching client capabilities", which I take to mean a certification/access tier we don't yet hold.
Could you tell me:
Happy to complete technical certification and a partner agreement. TIDAL is the primary service across our customer base, so we want to do this properly.
Ben Murray — Founder, BKM Solutions — control4@bkmsolutions.co.uk — +44 7843 622154
All reactions