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

# Audiomack API

Jentic publishes the only available OpenAPI specification for Audiomack API, keeping it validated and agent-ready. Audiomack is a music streaming and discovery platform focused on hip-hop, R&B, Afrobeats, and reggae, with a particularly strong catalog of independent and African-market artists. The Data API exposes catalog search, song, album, playlist, and artist metadata, plus trending and genre feeds for discovery surfaces. With nine endpoints it is enough to build a recommendation widget, an artist profile page, or an editorial dashboard backed by Audiomack data.

## For AI agents

Search Audiomack's catalog, fetch song, album, playlist, and artist metadata, and pull trending or genre feeds for music discovery surfaces.

## Scope

Does not handle uploads, monetisation reporting, or full audio file delivery - use for Audiomack catalog search, discovery, and metadata only.

## Capabilities

- Search the catalog for songs, albums, or artists via GET /music/search
- Pull a song's full metadata by slug with GET /music/song/{slug}
- Retrieve an album's tracklist and artwork via GET /music/album/{slug}
- Fetch a public playlist's contents through GET /music/playlist/{slug}
- List trending songs across the platform via GET /music/trending
- Get an artist profile with biography and stats from GET /artist/{slug}
- Page through an artist's full discography via /artist/{slug}/songs and /artist/{slug}/albums

## Use cases

### Music discovery widget

A media site or fan app embeds a 'trending now' widget that surfaces what is moving on Audiomack right now. GET /music/trending returns the platform-wide trending list, GET /music/genre/{genre} narrows it to Afrobeats, hip-hop, or reggae, and GET /music/song/{slug} fetches the artwork and stream URL for each tile. Together they power a real-time discovery surface without scraping the site.

Example prompt: Call GET /music/trending, take the top 10 results, and for each call GET /music/song/{slug} to return the song title, artist name, and artwork URL.

### Artist profile and discography page

An artist's website or EPK can be backed by live Audiomack data so the discography stays current with every new release. GET /artist/{slug} returns biography and stats, /artist/{slug}/songs paginates singles, and /artist/{slug}/albums returns full-length releases. The combination is enough to render a complete artist profile that updates automatically.

Example prompt: For artist slug 'burna-boy', call GET /artist/{slug} and GET /artist/{slug}/albums and return the artist bio plus a list of album titles and release dates.

### Editorial playlist surfacing

A curator or label wants to feature an Audiomack playlist on a third-party site. GET /music/playlist/{slug} returns the tracklist and curator metadata, and GET /music/song/{slug} fills in artwork and length per track. The agent assembles the embed in one workflow rather than copying tracks by hand each time the playlist changes.

Example prompt: Given playlist slug 'best-of-african-rhythms', call GET /music/playlist/{slug} and return the playlist title, owner, and an ordered list of song slugs with titles.

### AI agent integration via Jentic

A music-curation agent built on Jentic can call the Audiomack API without managing OAuth tokens directly. The agent searches an intent like 'search Audiomack for an artist', Jentic returns the matching GET /music/search operation with its input schema, and execution uses the OAuth token resolved from your Jentic One instance. The same flow works for trending and genre feeds.

Example prompt: Use Jentic search 'search for music on Audiomack', load the schema for GET /music/search, and execute it with q='asake'.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /music/search | Search the catalog for songs, albums, or artists |
| GET | /music/song/{slug} | Get song metadata and stream URL |
| GET | /music/album/{slug} | Get album metadata and tracklist |
| GET | /music/playlist/{slug} | Get playlist metadata and tracks |
| GET | /music/trending | List trending songs |
| GET | /artist/{slug} | Get artist profile and stats |
| GET | /artist/{slug}/songs | List an artist's songs |
| GET | /music/genre/{genre} | List music by genre |

## Key resources

- **Music** — Catalog search and direct lookup for songs, albums, playlists, trending, and genre feeds
- **Artists** — Artist profiles with paginated songs and albums

## Why Jentic

- **Setup:** Wiring Audiomack by hand means running its OAuth flow, refreshing tokens, and threading song, album, and artist slugs through its catalog paths. Through Jentic you install once, import the Audiomack API from the API Directory, store the credentials once, and your agent calls it.
- **Permission scoping:** Audiomack puts the resource slug in the URL path (/music/song/{slug}, /artist/{slug}), so a rule can pin your agent to reads for one artist or track. The spec exposes only GET reads over catalog metadata, so no write operation is available regardless of what you allow.
- **Credential handling:** Your Audiomack OAuth token is stored once, encrypted, by your own Jentic One instance, which refreshes it and injects the access token at execution time. The raw token never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'search for music on Audiomack', and Jentic returns the matching operation with its input schema so the agent picks /music/search, /artist/{slug}, or /music/trending without reading the reference docs.

## Related APIs

- **Spotify Web API** — Spotify is the larger global music catalog with deeper recommendation and playback features.
- **SoundCloud API** — SoundCloud is the closest peer for independent and creator-uploaded music catalogs.
- **Castos API** — Castos handles podcast hosting and distribution that pairs with Audiomack music workflows.

## FAQ

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

Audiomack publishes the Data API documentation at audiomack.com/data-api/docs but does not distribute an OpenAPI file. Jentic generates and maintains this spec so that AI agents and developers can call Audiomack 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 Audiomack API use?

The Audiomack Data API uses OAuth 2.0 with an access token passed as a Bearer header. Apps register on the Audiomack developer portal to receive client credentials. Through Jentic the OAuth token is stored in the vault and injected at execution time.

### Can I get trending songs by genre with the Audiomack API?

Yes. GET /music/trending returns platform-wide trending, and GET /music/genre/{genre} narrows the trending feed to a genre such as afrobeats or hip-hop. Both endpoints return song slugs you can hydrate with GET /music/song/{slug}.

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

Audiomack does not publish rate limits inside the OpenAPI spec; per the developer documentation the API is throttled per OAuth client and returns 429 with a Retry-After header when the limit is hit. Cache discovery responses where possible to stay within the limit.

### How do I pull an artist's discography through Jentic?

Run jentic search 'list an artist's songs on Audiomack', load the schema for GET /artist/{slug}/songs, and execute it with the artist slug. To include albums, repeat with GET /artist/{slug}/albums. With pip install jentic an agent can build the discography view in two async calls.

### Is the Audiomack Data API free?

Audiomack offers free Data API access for approved developer applications. Commercial or high-volume use cases require sign-off from Audiomack and may move onto a partnership tier with higher quotas.

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

Yes. Because you run Jentic One yourself, your own rules decide which Audiomack operations and credentials the agent may use. The API exposes only GET reads over catalog metadata, so no write operation exists to grant regardless of your rules. And since Audiomack puts the resource slug in the URL path, such as /music/song/{slug} and /artist/{slug}, you can pin the agent to reads for a single artist or track rather than the whole catalog.