canonical: https://jentic.com/apis/napster.com/napster

# Napster API

Jentic publishes the only available OpenAPI specification for Napster API, keeping it validated and agent-ready. The Napster API exposes the Napster music catalogue and user library, covering artists, albums, tracks, genres, playlists, and listening history. Public catalogue endpoints are reachable with an API key (apikey query parameter) while user-scoped endpoints under /me require an OAuth2 access token. Agents can search the catalogue, look up rich metadata for artists and albums, retrieve top tracks per genre, and read a logged-in user's saved library and listening history.

## For AI agents

Search and retrieve metadata from the Napster music catalogue or read a user's saved library and listening history.

## Scope

Does not handle audio playback streaming, music licensing, or audio fingerprinting - use for catalogue metadata and user library reads only.

## Capabilities

- Search the Napster catalogue for matching artists, albums, and tracks in a single request
- Retrieve full artist details including biography, images, top tracks, and similar artists
- Look up album metadata, track listings, and album cover artwork
- Browse top tracks, top artists, and new releases for any genre
- Read a logged-in user's saved library of artists, albums, and tracks
- Surface a user's recent listening history for personalised recommendations

## Use cases

### Music Discovery and Recommendation

Music apps and chat assistants surface recommendations based on a user's tastes by combining genre top-track lists with similar-artist endpoints. The /artists/{artistId}/similar and /genres/{genreId}/tracks/top endpoints return ranked results that can be merged into a recommendation feed without running a custom recommendation model. Catalogue calls only need the apikey query parameter so integration is straightforward.

Example prompt: Call GET /artists/{artistId}/similar then GET /artists/{similarId}/tracks/top to assemble a 20-track playlist of similar artists' best work.

### Catalogue Metadata Enrichment

Streaming and editorial platforms use Napster's catalogue endpoints to enrich their own track or album records with artist biographies, cover artwork, and release dates. The /albums/{albumId}/images and /artists/{artistId}/bio endpoints return structured metadata that can backfill missing fields in a third-party catalogue or power editorial pages.

Example prompt: Fetch GET /artists/{artistId}/bio and GET /artists/{artistId}/images for each artist in a catalogue and store the biography and image URLs alongside the local artist record.

### User Library and Listening History

Apps that build music dashboards or year-in-review summaries read a user's library and recent listening history through the /me endpoints. These require an OAuth2 access token tied to the user's Napster account so user-specific data stays scoped to the authenticated session. The endpoints return paginated lists of artists, albums, tracks, and recent plays.

Example prompt: Call GET /me/listening-history and aggregate plays by artist over the past 30 days for a personal music dashboard.

### AI Agent Music Assistant

An AI assistant invoked through Jentic answers natural-language music questions like 'what are the top jazz tracks this week?' by searching for the matching Napster operation, loading its schema, and executing it. Catalogue endpoints work without a user OAuth flow because the apikey is stored in your Jentic One instance as the API key credential.

Example prompt: Search Jentic for 'search music catalogue', load GET /search, and execute it with the user's natural-language query to surface matching tracks, albums, and artists.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /search | Search the catalogue across artists, albums, and tracks |
| GET | /artists/{artistId} | Get artist details |
| GET | /artists/{artistId}/similar | Get similar artists |
| GET | /albums/{albumId} | Get album details |
| GET | /albums/{albumId}/tracks | Get tracks on an album |
| GET | /genres/{genreId}/tracks/top | Get top tracks for a genre |
| GET | /me/library/tracks | Get the user's library tracks (OAuth2) |
| GET | /me/listening-history | Get the user's listening history (OAuth2) |

## Key resources

- **Search** — Search the catalogue across artists, albums, and tracks
- **Artists** — Artist details, top tracks, similar artists, biography, and images
- **Albums** — Album metadata, track listings, images, and top/new releases
- **Tracks** — Track details and top tracks lists
- **Genres** — Genre listings, top artists, and top tracks per genre
- **Playlists** — Playlist details and track listings
- **Members** — User library and listening history under /me (OAuth2)

## Why Jentic

- **Setup:** Wiring Napster by hand means holding its apikey query value plus OAuth2 access tokens, appending them correctly on every call against api.napster.com, and mapping the catalogue and user-library reads yourself. Through Jentic you install once, import the Napster API from the API Directory, store the credentials once, and your agent calls it.
- **Permission scoping:** Napster puts the resource id in the URL path (/artists/{artistId}, /albums/{albumId}/tracks), so a rule can pin your agent to one artist or album. You choose the operations it may call, so user-library reads under /me are not included unless you add them.
- **Credential handling:** Your Napster apikey and OAuth2 access tokens are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'search the music catalogue' or 'get a user's listening history', and Jentic returns the matching Napster operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Spotify Web API** — Music catalogue and user library API with broader catalogue and richer audio features
- **SoundCloud API** — User-uploaded music and audio platform
- **Musixmatch API** — Lyrics catalogue API

## FAQ

### Why is there no official OpenAPI spec for Napster API?

Napster does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Napster API via 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 Napster API use?

Catalogue endpoints accept an API key passed as the 'apikey' query parameter. User-scoped endpoints under /me (library, listening history) require OAuth2 access tokens tied to a Napster account. Both credentials are stored encrypted in your Jentic One instance when called via Jentic.

### Can I read a user's library through the Napster API?

Yes, via GET /me/library/artists, GET /me/library/albums, and GET /me/library/tracks. These endpoints require a valid OAuth2 access token. The /me/listening-history endpoint exposes recent plays for the authenticated user.

### How do I get similar artists with the Napster API?

Call GET /artists/{artistId}/similar with the artist ID returned from /search or /artists/top. The response is a ranked list of artist objects you can iterate through to build recommendations or related-artist sections.

### What are the rate limits for the Napster API?

The OpenAPI spec does not declare rate limits. Refer to the developer.napster.com portal for the current per-key quota. Cache catalogue responses (artists, albums, genres) aggressively because the metadata changes infrequently.

### How do I search the Napster catalogue through Jentic?

Run jentic.search('search music catalogue'), load the GET /search operation, then jentic.execute with a query string and the result types you want (artist, album, track). Jentic injects the apikey from the vault and returns the parsed search response.

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

Yes. Because you run Jentic One yourself, your own rules decide which Napster operations and credentials the agent may use, so you can grant read-only catalogue calls like GET /search and GET /artists/{artistId} while leaving the OAuth2 user-library and listening-history reads under /me out entirely unless you add them. Since Napster puts the resource id in the URL path, such as /artists/{artistId} or /albums/{albumId}/tracks, a rule can pin the agent to a single artist or album. The API key and OAuth2 tokens stay stored in your instance and are injected only for the operations you allow.