canonical: https://jentic.com/apis/mixcloud.com/mixcloud # Mixcloud API Jentic publishes the only available OpenAPI specification for Mixcloud API, keeping it validated and agent-ready. The Mixcloud API gives access to Mixcloud's music and DJ-mix streaming platform: cloudcasts (mixes and shows), user profiles, social graph (followers, following, favorites, listens), comments, search, and uploads. Read endpoints are public; write actions like upload, follow, and favorite use OAuth 2.0 to act on behalf of a Mixcloud user. ## For AI agents Read Mixcloud cloudcasts, user profiles, and social graph data, and act on behalf of a user to upload mixes, follow accounts, or favorite shows via OAuth 2.0. ## Scope Does not handle music licensing, royalty reporting, or ad insertion - use for Mixcloud cloudcast read, social graph, and OAuth-scoped upload only. ## Capabilities - Retrieve a user's public profile and statistics - List a user's cloudcasts (uploaded mixes and shows) - Read followers, following, favorites, and listen history - Search Mixcloud for users, cloudcasts, and tags - Upload a new cloudcast on behalf of an authenticated user - Follow, unfollow, favorite, and comment via OAuth-scoped calls - Browse cloudcasts by category ## Use cases ### Music Discovery and Aggregation Build a discovery feed that pulls a user's favorite Mixcloud DJs, lists their latest cloudcasts, and surfaces shared followers. The public read endpoints under /{username} and /{username}/cloudcasts return paginated JSON so a recommender can refresh nightly without OAuth and only escalate to user auth for personalised actions. Example prompt: Call GET /{username}/following and then GET /{username}/cloudcasts for each followed account to build a feed of new mixes ### Show Upload Automation A radio show or podcast workflow uploads a new cloudcast to Mixcloud at the end of each recording session. After OAuth handshake the upload endpoint accepts the audio file plus metadata such as title, tags, and tracklist so the publishing step becomes a single API call rather than a manual web upload. Example prompt: Use the OAuth user token to POST /upload with the recorded mix file, title, and tracklist for the latest episode ### Social Graph Analytics Pull followers, following, favorites, and listens for a set of accounts to analyse audience overlap and engagement. The endpoints return the underlying user objects with stats so an analyst can compute network metrics without scraping the website. Useful for label A and R, talent scouting, and audience research. Example prompt: Call GET /{username}/followers and GET /{username}/listens for each account in the watchlist and compute weekly growth deltas ### Agent-Driven Content Workflows An agent discovered through Jentic ingests a podcast episode, attaches metadata, and pushes it to Mixcloud as a cloudcast. Jentic stores the OAuth refresh token in its credential vault and the agent only invokes the upload operation, so the user's Mixcloud account credentials never enter the agent's runtime context. Example prompt: Use Jentic to find the Mixcloud upload operation and execute it with the rendered episode mp3 and metadata for user @djname ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/{username}` | Get a user's public profile | | GET | `/{username}/cloudcasts` | List a user's cloudcasts | | GET | `/{username}/followers` | List a user's followers | | GET | `/{username}/favorites` | List a user's favorites | | GET | `/{username}/{cloudcast_slug}` | Get a specific cloudcast | | GET | `/{username}/{cloudcast_slug}/comments` | List comments on a cloudcast | ## Key resources - **Users** — User profiles and stats accessed by username - **Cloudcasts** — Mixes, shows, and podcast episodes - **Search** — Search across users, cloudcasts, and tags - **Upload** — OAuth-scoped cloudcast upload - **Social** — Followers, following, favorites, and listens - **Categories** — Browse cloudcasts by category ## Why Jentic - **Setup:** Wiring the Mixcloud API by hand means running its OAuth2 flow, refreshing tokens, and mapping username and cloudcast slugs into every request yourself. Through Jentic you install once, import the Mixcloud API from the API Directory, store the OAuth credentials once, and your agent calls it. - **Permission scoping:** Mixcloud puts the username and cloudcast slug in the URL path (/{username}/{cloudcast_slug}), so a rule can pin your agent to one account's cloudcasts: it can read that account's shows, followers, and favorites. You choose the operations it may call, so OAuth-scoped upload is not included unless you add it. - **Credential handling:** Your Mixcloud OAuth credentials 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 'get a Mixcloud user's cloudcasts' or 'read comments on a show', and Jentic returns the matching Mixcloud operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **SoundCloud API** — Audio hosting, user profiles, and social graph - **Spotify Web API** — Streaming catalogue, playlists, and user library - **OpenAI API** — Speech-to-text and embeddings for audio metadata ## FAQ ### Why is there no official OpenAPI spec for Mixcloud API? Mixcloud does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Mixcloud 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 Mixcloud API use? Read endpoints under /{username} are public and need no auth. Write actions such as upload, follow, and favorite use OAuth 2.0 with a user-scoped access token. Through Jentic the OAuth token is stored in the credential vault and injected at execution time. ### Can I upload a cloudcast through the Mixcloud API? Yes. Once you have an OAuth user token call the upload endpoint with the audio file and metadata such as title, picture, tags, and tracklist. The cloudcast appears under the authenticated user's profile. ### What are the rate limits for the Mixcloud API? Mixcloud applies per-application and per-user rate limits that vary by endpoint family. Public reads have generous quotas; uploads and writes are stricter. Cache profile and cloudcast responses where possible to avoid hitting limits during analytics jobs. ### How do I read a user's followers through Jentic? Search Jentic for list mixcloud followers, load the schema for GET /{username}/followers, and execute with the username path parameter. Pagination cursors are returned in the response for follow-up calls. ### Does the Mixcloud API support search? Yes. Use the search endpoints to query users, cloudcasts, and tags by keyword. Results include usernames and cloudcast slugs that can be passed to the per-user and per-cloudcast endpoints for richer detail. ### Can I limit what my agent is allowed to do with the Mixcloud API? Yes. Because Jentic One is self-hosted, your own rules decide which Mixcloud operations and credentials the agent may use. Since Mixcloud puts the username and cloudcast slug in the URL path, you can pin the agent to a single account and let it read only that account's cloudcasts, followers, and favorites. You choose the operations it may call, so the OAuth-scoped upload endpoint is not available to the agent unless you explicitly add it.