Get started

Hoopr B2B API

Integrate Hoopr's licensed music catalog into your product. Authenticate once, then browse, search and stream tracks, playlists and filters over a clean REST API.

Base URL & protocol

HTTPS only, JSON request/response. The version prefix is part of each route path (e.g. /v1/tracks) — the base URL is just your assigned host: https://<your-b2b-host>.

What you can build

The Hoopr B2B API gives your application server-to-server access to our music catalog. Typical integrations include music search and discovery in your product, background-music pickers for video tools, curated playlist surfaces, and licensing workflows.

AuthenticationOAuth2 client-credentials. One token, one hour.Search the catalogFree-text + structured filters by genre, mood, BPM.PlaylistsCurated and custom playlists, paginated.FiltersEvery genre, mood and use-case in one call.

Core principles

Server-to-server. All calls are made from your backend. Never embed your client_secret in a browser, mobile app or any client-side code.
One base URL, two modes. Test vs. live is decided by which secret you authenticate with — just like Stripe and Razorpay.
One response envelope. Every response is { data, error }, so success and error handling are identical across endpoints.
Versioned per route. Endpoints carry their own version prefix so individual routes can evolve to /v2 independently.

The shape of every response

Successful and failed calls share one structure, which keeps your client code simple:

{
  "data":  { /* the result */ },
  "error": { "code": 0, "message": "OK" }
}

Get your credentials

Your Hoopr account manager issues a client_id and a client_secret. The secret is shown only once. When you have them, head to the quickstart.

Start the quickstart Request credentials

Next Quickstart