canonical: https://jentic.com/apis/7digital.com/7digital

# 7digital API

Jentic publishes the only available OpenAPI specification for 7digital API, keeping it validated and agent-ready. The 7digital API exposes the music store and catalogue services from 7digital across seven endpoints covering search and detail retrieval for tracks, releases, and artists. Apps use it to power music search, browse artist catalogues, and look up release tracklists for both download and streaming products. Authentication is OAuth using a 7digital consumer key issued through the partner portal.

## For AI agents

Search the 7digital catalogue, look up artists, releases, and tracks, and retrieve release tracklists for music apps and streaming products.

## Scope

Does not handle audio playback streams, music licensing negotiation, or user playlist storage - use for catalogue search and metadata retrieval only.

## Capabilities

- Search the 7digital catalogue for tracks matching a free-text query
- Search for artists by name with relevance ranking
- Search for releases (albums and EPs) across the catalogue
- Retrieve full release detail including label, release date, and territory availability
- Browse an artist's discography and biography
- List the tracks on a specific release with duration and ISRC where available

## Use cases

### Music Search Inside a Consumer App

Music streaming and download apps power their search bar with the 7digital track, artist, and release search endpoints so users can find content from across the licensed catalogue in a single query. The API returns ranked results with cover art and preview URLs that apps can render directly. A first working search experience takes one to two days to ship.

Example prompt: Call /track/search with the user's query 'happier than ever', display the top ten results, and resolve the selected track via /release/details for full metadata.

### Artist Pages and Discography Browsing

Fan apps and music magazines build artist pages by combining /artist/browse and /artist/releases to show biographies, discographies, and the latest releases. The endpoints return structured records with consistent IDs so an editorial team does not need to maintain a separate catalogue. Initial integration takes about two days.

Example prompt: Call /artist/browse for 'Radiohead', then /artist/releases sorted by release date to render a discography page.

### Release Detail Pages with Tracklists

Album-detail pages in music apps use /release/details and /release/tracks to show metadata, label, release date, and the full tracklist with durations. This replaces hand-curated content and ensures the tracklist stays in sync with the licensed catalogue. End-to-end integration is around a day for a single album view.

Example prompt: Given a selected album, call /release/details and /release/tracks and render the page with cover art, tracklist, and duration totals.

### AI Music Assistant via Jentic

An AI music assistant connected through Jentic can answer questions like 'find me Adele's latest album and its tracks' by chaining /artist/search, /artist/releases, and /release/tracks behind the scenes. Jentic stores the OAuth consumer credentials in the vault and exposes the operations by intent. End-to-end response time is a few seconds per query.

Example prompt: Search Jentic for 'find an album and tracklist', load /artist/search for 'Adele' to get the artist ID, then load /artist/releases and /release/tracks to return the latest album and its tracks.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /track/search | Search the catalogue for tracks |
| GET | /release/search | Search the catalogue for releases |
| GET | /artist/search | Search for artists by name |
| GET | /release/details | Retrieve full release metadata |
| GET | /artist/browse | Browse an artist record with biography |
| GET | /artist/releases | List releases for a given artist |
| GET | /release/tracks | List tracks for a specific release |

## Key resources

- **Track Search** — Free-text search across the 7digital track catalogue
- **Artist** — Artist search, browse, and discography retrieval
- **Release** — Release search, detail retrieval, and tracklist lookup

## Why Jentic

- **Setup:** Wiring the 7digital API by hand means implementing OAuth 1.0 request signing with your consumer key and secret and shaping catalogue search and metadata requests yourself. Through Jentic you install once, import the 7digital API from the API Directory, store the consumer credentials once, and your agent calls it.
- **Permission scoping:** 7digital carries search terms and release or artist ids in query parameters rather than a resource id in the path, so limit the agent to the operations it needs, such as track or release search and metadata lookups. You choose the allowed set, so only the operations you pick can run.
- **Credential handling:** Your 7digital OAuth consumer key and secret are stored once, encrypted, by your own Jentic One instance and used to sign requests at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'search music by track title' or 'get an album tracklist', and Jentic returns the matching 7digital operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **MusicBrainz API** — Open music metadata database with artist, release, and track records
- **Napster API** — Music catalogue and streaming API with similar search and detail coverage
- **eBay API** — E-commerce platform commonly used to sell physical music products

## FAQ

### Why is there no official OpenAPI spec for 7digital API?

7digital publishes a developer portal at docs.7digital.com but does not distribute a machine-readable OpenAPI specification for direct ingestion. Jentic generates and maintains this spec so AI agents and developers can call 7digital through structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the 7digital API use?

The API uses OAuth signed requests with a consumer key and secret issued through the 7digital partner portal. When called through Jentic the OAuth credentials are stored encrypted in the vault and the request signature is generated at execution time, so the secret never enters the agent's prompt context.

### Can I search the 7digital catalogue by track title with this API?

Yes. Call GET /track/search with the q parameter set to the track title. The response returns ranked matches with track ID, artist, release, duration, and preview URLs that your app can render.

### What are the rate limits for the 7digital API?

Rate limits are set per partner contract rather than as a single public number. 7digital advises caching catalogue responses where possible and avoiding tight polling loops. Back off on HTTP 429 responses and respect the Retry-After header.

### How do I get an album tracklist with the 7digital API through Jentic?

After running pip install jentic and setting JENTIC_AGENT_API_KEY, search Jentic for 'get album tracklist', load GET /release/tracks, and execute it with the release ID. Jentic injects the OAuth signing automatically.

### Does the 7digital API stream audio directly?

No. The catalogue API returns metadata and short preview URLs only. Full track playback for download or streaming products is delivered through 7digital's separate playback APIs once a partner subscription is in place.

### Can I limit what my agent is allowed to do with the 7digital API?

Yes. Because you run Jentic One yourself and self-host the execution layer, your own rules decide which 7digital operations and credentials the agent may use. The 7digital API passes search terms and release or artist IDs as query parameters rather than in the path, so you can restrict the agent to only the operations it needs, such as track, release, and artist search or metadata lookups like /release/details and /release/tracks. Only the operations you pick can run, and your OAuth consumer key stays with your instance rather than the agent's context.