Songlink / Odesli API

Name: Songlink / Odesli API API
Brand: Songlink / Odesli API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMediaAudio ProcessingapiKey1 EndpointsREST

For Agents

Convert a music link from any streaming service into equivalent links on Spotify, Apple Music, YouTube, Deezer, Tidal, Amazon, and others.

Quickstart

Get started with Songlink / Odesli API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"convert this music link to all streaming services"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Songlink / Odesli API 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

GET STARTED

Start building with Songlink / Odesli API API

Explore with Jentic

View OpenAPI Document

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 document 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.

Use Cases

Patterns agents use Songlink / Odesli API 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 managing the API key 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 — Jentic handles the api_key query parameter from the encrypted vault.

Search Jentic for the Odesli links operation, load the schema, and execute it for a user-supplied Spotify URL

Key Endpoints

1 endpoints — songlink / odesli api resolves a song, album, or artist link from one streaming service into the equivalent links across every other supported service.

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 though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Odesli API keys are stored encrypted in the Jentic vault and appended to the api_key query parameter at request time. The raw key never appears in the agent's request log.

Intent-based discovery

The API has only one endpoint, so discovery is trivial — the value is in not having to manage the api_key, rate-limit logic, and country-bias parameter manually. Agents search Jentic by intent and execute.

Time to first call

Direct integration is already short (one endpoint), but provisioning a key, handling 429s, and shaping the response still takes 1-2 hours. Through Jentic: under 10 minutes.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Spotify Web API

Provides full Spotify catalogue and user library access that pairs with Odesli's cross-service link resolution

Use Spotify directly to search the catalogue, manage playlists, or read user library. Use Odesli when the agent needs the same track represented on Apple Music, YouTube, or Tidal.

Alternative

Apple App Store Connect API

Apple's developer surface for app and media metadata when working inside the Apple ecosystem

Use App Store Connect for Apple-only catalogue and app metadata. Use Odesli when the requirement is multi-platform link resolution for a single track.

Complementary

Facebook Graph API

Pair social sharing with cross-platform music links for richer social posts

Use the Facebook Graph API to publish a post containing a song.link URL produced by Odesli, so recipients on any service can open the track.

FAQs

Specific to using Songlink / Odesli API API through Jentic.

What authentication does the Odesli API use?

The API uses an API key passed as the api_key query parameter on the /links endpoint. A free no-key tier is available with strict per-IP rate limiting, while a paid key removes that cap. Through Jentic, the API key is stored encrypted in the vault and appended at request time.

Can I look up a track by ISRC with the Odesli API?

Yes. The /links endpoint accepts type and id parameters in addition to the url parameter. Pass type=song with an ISRC-derived id, or send a platform URL containing the ISRC, and the response includes matched links and per-platform IDs.

What are the rate limits for the Odesli API?

The free no-key tier is limited to roughly 10 requests per minute per IP and is intended for development. Paid keys raise this limit substantially — contact Odesli for production-tier pricing. Cache responses where possible since track-to-link mappings are stable.

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 contains entitiesByUniqueId with each platform's URL and id; iterate to pick the target service.

Which streaming services does the Odesli API support?

The API resolves links across Spotify, Apple Music, YouTube, YouTube Music, Deezer, Tidal, Amazon Music, SoundCloud, Pandora, Napster, Yandex, and a few smaller regional services. Coverage varies by region — pass userCountry to bias the response toward a specific market.