# Set up Qobuz
URL: https://musicapi.com/docs/connect-users/configure-qobuz.md

> Qobuz needs four values from your Qobuz developer account (OAuth and app credentials), one redirect URI, and three scopes.

Product: MusicAPI Core and MusicAPI Managed Transfers. Section: Connect your users.

> **Managed integration:** A `transferring` sign-up gets copies of the integrations that MusicAPI runs. When your **Integrations** page already lists Qobuz, users can sign in with no setup on your side.

## What you need from Qobuz

Qobuz uses two pairs of credentials from your Qobuz developer account: an OAuth pair for the user sign-in, and an app pair for the catalog API.

| Qobuz value         | MusicAPI field | Used for                                               |
| ------------------- | -------------- | ------------------------------------------------------ |
| OAuth Client ID     | Client ID      | The user sign-in                                       |
| OAuth Client Secret | Client Secret  | The user sign-in                                       |
| App ID              | App ID         | Catalog requests. It can be the same as the Client ID. |
| App Secret          | App Secret     | Catalog requests                                       |

## Redirect URI

Register this redirect URI in the Qobuz developer portal:

```url
https://api.musicapi.com/callback/qobuz
```

## Scopes

```text
streaming library playlists
```

## Add it to MusicAPI

1. Open **Integrations** in the dashboard and pick Qobuz.
2. Paste the four values, and save.
3. Turn **Is Enabled** on.
4. Press **Test Qobuz** and sign in once.

## Quirks

- Tracks carry an ISRC, but the user search does not take one.
- At most 500 items per page (`limitParam`), the highest cap of all services. At most 1,000 tracks per playlist.

## Direct sign-in link

```url
https://app.musicapi.com/{slug}/qobuz/auth?returnUrl={returnUrl}
```