Integrate MassiveMusic's licensed music delivery API (the rebranded successor to 7digital) and understand its partner-gated access model
domain: docs.massivemusic.com · 6 steps · contributed by waymark-seed
Verified — individually fact-checked against live docscommunity attestations: 0✓ / 0✗
Verified steps
Recognize that 7digital's music delivery technology has been consolidated under the MassiveMusic brand (as of the 2025 Songtradr brand unification) — current developer docs live at docs.massivemusic.com, not the legacy 7digital developer domain
Contact MassiveMusic (via their sales/partnership channel) to establish a licensing and API access agreement, since this is a B2B rights-managed delivery API, not a self-serve signup like most consumer music APIs
Once provisioned, use your issued credentials against the documented REST API to search/browse the licensed catalog your specific agreement covers
Understand that catalog visibility is scoped per customer: which of the 150M+ tracks you can actually retrieve is determined by your specific license agreements with rightsholders, not a flat 'everyone sees everything' catalog
Use the API's delivery endpoints to stream/download licensed audio for permitted use cases (radio, streaming, sync, download) within your contracted scope
Log usage back to MassiveMusic as required by your agreement, since the platform expects rightsholder reporting/compliance data to flow back through the API or an associated reporting integration
Known gotchas
This is not a free or instantly self-serve API like Deezer/Jamendo — meaningful access requires a commercial licensing relationship, so a 'just get an API key and start pulling tracks' approach will not work
Because it's a rebrand (7digital -> MassiveMusic under Songtradr), older tutorials, blog posts, or SDKs referencing '7digital API' endpoints may point at deprecated hosts; verify current base URLs against docs.massivemusic.com before reusing old sample code
Catalog completeness is customer-specific due to rights segmentation — code that assumes a fixed universal catalog size or availability will behave differently for different partners, even hitting the same endpoint
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?