Authenticate with the Audiomack API using OAuth 1.0a and fetch trending music
domain: audiomack.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Register your application to get an Audiomack API key/secret pair for OAuth 1.0a signing
Request an unauthorized request token from the OAuth request-token endpoint, supplying an `oauth_callback` URL (request tokens are short-lived, valid about an hour)
Redirect the user to Audiomack's authorization page with the request token so they can approve your app
Exchange the authorized request token for a long-lived access token via the access-token exchange endpoint, signing the request per OAuth 1.0a rules (HMAC-SHA1 signature over the request parameters)
Call `GET https://api.audiomack.com/v1/music/trending` (optionally filtered by genre) using your OAuth 1.0a-signed request to list currently trending tracks
Use the corresponding recently-uploaded/genre-filtered endpoints the same way when you need newest-upload feeds instead of trending
Known gotchas
This API uses OAuth 1.0a, not OAuth 2 — every request needs a valid HMAC signature built from your consumer secret and token secret, which is easy to get subtly wrong (parameter encoding/ordering) compared to bearer-token APIs
Request tokens expire quickly (about an hour) — a slow redirect/approval step in your auth UI can cause the token exchange to fail and require restarting the flow
Trending and upload-listing endpoints are genre-filterable but the exact set of supported genre identifiers should be confirmed against current docs before hardcoding a genre list
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?