Odesli Songlink / Odesli API
Agent-ready OpenAPI document · curated by JenticMediaAudio ProcessingapiKey1 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Convert a music link from any streaming service into equivalent links on Spotify, Apple Music, YouTube, Deezer, Tidal, Amazon, and others.
Use for: I need to convert this Spotify link into an Apple Music link, Get all streaming-service links for the song at this YouTube URL, Find the song.link share URL for a Tidal album, Look up a track by ISRC across every streaming platform
Not supported: Does not stream or download music, manage user libraries, or handle licensing payments - use for cross-service music link and metadata resolution only.
Jentic publishes the only available OpenAPI specification for Songlink / Odesli API, keeping it validated and agent-ready. Songlink / Odesli API resolves a song, album, or artist link from one streaming service into the equivalent links across every other supported service. Send any Spotify, Apple Music, YouTube, Deezer, Tidal, Amazon Music, or SoundCloud URL and the API returns matching URLs and platform metadata for the same content. It powers the song.link share-link experience and any app that needs cross-platform music discovery.
Install Jentic One Beta
Connect the Songlink / Odesli API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Songlink / Odesli API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fodesli.co%2Fodesli" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fodesli.co%2Fodesli" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Songlink / Odesli API.
Resolve a Spotify or Apple Music URL into matched links across 10+ platforms
Look up an entity by ISRC, UPC, or platform-specific ID without a URL
Return album art, artist names, and track titles alongside the matched links
Generate a universal song.link share URL for any input link
Enrich a music recommendation with links the user can open in their preferred service
Set userCountry so matching reflects a target country's catalogue availability
Use Cases
Patterns agents use Songlink / Odesli API for, with concrete tasks.
★ Universal music share links
Generate a single song.link URL from any streaming-service link so recipients can open the track in whichever app they use. The API takes an input URL, returns a song.link page URL, and includes per-platform direct links the recipient sees on the share page. This removes the friction of users sending Spotify links to friends on Apple Music.
Take a Spotify track URL and return the song.link page URL plus the matching Apple Music and YouTube Music URLs
Music recommendation enrichment
Enrich AI-generated music recommendations with playable links across every major service. When an LLM suggests a track, the API resolves it into Spotify, Apple Music, YouTube, and Tidal links so the user can open it in their preferred app. The 1-endpoint surface keeps integration trivial.
Given the track title 'Blinding Lights' by The Weeknd, find its Spotify URL externally and then call the Odesli API to retrieve all matching streaming-platform URLs
Catalogue cross-referencing by ISRC
For music-tech teams managing playlists or analytics, look up a track by ISRC and retrieve every platform's identifier in one call. This avoids per-service catalogue search and gives a stable cross-platform key. The response includes platform-specific IDs that downstream systems can store.
Resolve the ISRC USRC17607839 into Spotify, Apple Music, and Deezer track IDs
AI agent music discovery via Jentic
AI agents acting as music assistants use Jentic to call the Odesli API without handling the credential directly. The agent searches Jentic for 'find this song on every service', loads the schema for the /links endpoint, and executes with the input URL - your own Jentic One instance appends the optional key query parameter it holds encrypted.
Search Jentic for the Odesli links operation, load the schema, and execute it for a user-supplied Spotify URL
Key Endpoints
1 endpoints — jentic publishes the only available openapi specification for songlink / odesli api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/links
Resolve a music URL or platform ID into matched links across all supported streaming services
GET
/links
Resolve a music URL or platform ID into matched links across all supported streaming services
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Songlink / Odesli API by hand means appending its key query parameter, handling rate limits, and setting the country-bias parameter on the single /links endpoint yourself. Through Jentic you install once, import Odesli from the API Directory, store the API key once, and your agent calls it.
Permission scoping
The Odesli API exposes a single read operation with no resource id in the URL path, so scoping is by operation: you limit the agent to the one operation it needs, resolving cross-service music links, and it can call nothing else.
Credential isolation
Your Odesli API key is stored once, encrypted, by your own Jentic One instance and appended to the key query parameter at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'get streaming links for this song', and Jentic returns the /links operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Songlink / Odesli API through Jentic.
What authentication does the Odesli API use?
Odesli's docs state you do not need any special authentication or authorization for the API, so unauthenticated calls to /links are the documented default. An optional API key can be sent as the key query parameter on /links for higher rate limits and preferred support. The docs also state that Odesli has stopped giving out API keys, and that sustained access is requested through the allowlisting form in its Sunsetting the Songlink (Odesli) public API help article. Where you do hold a key, your own Jentic One instance stores it encrypted and appends it at request time.
Can I look up a track by ISRC with the Odesli API?
Yes. Where you do not pass url, the docs require platform, type and id together. isrc and upc are both listed as supported platform values, and type accepts song or album, so an ISRC lookup is platform=isrc with type=song and the ISRC as id. The response returns linksByPlatform plus per-platform identifiers in entitiesByUniqueId.
What are the rate limits for the Odesli API?
Without an API key the documented rate limit is 10 requests per minute. Odesli's docs say the limit with an API key is higher, without publishing a number. The same docs add that while the v1-alpha.1 namespace is deprecated, requests are subject to stricter per-IP daily limits and over-quota requests return 429 Too Many Requests. Cache responses where you can, since track-to-link mappings are stable.
Is the Odesli API being retired?
Odesli's API doc carries a deprecation notice for the whole v1-alpha.1 namespace, giving an announced retirement date of July 31, 2026, after which it says all v1-alpha.1 endpoints return 410 Gone. The endpoint was still returning HTTP 200 with full link data when Jentic last checked it on 2026-08-12. Treat the surface as deprecated but answering: handle 410 and 429 responses in your agent's error path.
Is there an Odesli MCP server?
You don't need an MCP server to give your agent the Odesli API. Jentic connects it directly from the API Directory: import Odesli, store your optional key once, and your agent calls the /links operation without another server's tool definitions loaded into its context.
Why is there no official OpenAPI specification for the Odesli API?
Odesli documents the API as a help-centre page rather than a machine-readable file: the reference is a Notion doc reached from odesli.co/help and from the songlink/docs repository on GitHub, and no OpenAPI document is published alongside it. Jentic wrote and validated the specification in the API Directory from that documentation, covering the single GET /links operation and its url, platform, type, id, userCountry, songIfSingle and key query parameters.
How do I convert a Spotify link to other services through Jentic?
Search Jentic for 'convert music link', load the schema for the /links operation, and execute with the Spotify URL as the url parameter. The response returns linksByPlatform, keyed by platform, with a url for each match; read the key for the service you want.
Which streaming services does the Odesli API support?
The documented platform list is spotify, itunes, appleMusic, youtube, youtubeMusic, google, googleStore, pandora, deezer, tidal, amazonStore, amazonMusic, soundcloud, napster, yandex, spinrilla, audius, anghami, boomplay, audiomack, bandcamp, plus isrc and upc as identifier types. A platform key appears in the response only where a match was found, and userCountry sets the country used when searching streaming catalogues.
Can I limit what my agent is allowed to do with the Odesli API?
Yes. The Odesli API exposes a single read-only operation, the /links endpoint, with no resource id in the path, so you scope access by operation from your own self-hosted Jentic One instance. You write the rules that decide the agent may call only the links-resolution operation, turning any music URL or platform ID into matched cross-service links, and nothing else. Because your Jentic One holds the optional key query parameter and appends it at request time, the agent never sees the credential and cannot reach operations you have not allowed.
GET STARTED