# Playing and accessing tracks | AudioDN Docs

> Choose how access is granted — Client-Side Player key, server-created play session, or signed delivery without a play session — and how audio is played.

Source: https://audiodeliverynetwork.com/docs/integration/playback/

---

# Playing and accessing tracks

Choose how access is granted, then — when a server creates a play session — how audio is played. Upload is a separate decision; see [Uploading tracks](/docs/integration/uploading).

#### Play sessions vs signed delivery

A **play session** is a short-lived, per-listener authorization created via the API (`track` or `collection` scope — playlist scope is reserved and returns 400). **Signed delivery without a play session** signs a URL on your server with a URL Signing key; possession of the temporary link is sufficient access. You can mix both (for example signed previews and gated full tracks).

## Playing and accessing tracks

Choose how access is granted, then — if needed — how audio is played. You can mix methods (for example public signed previews and gated play sessions for full tracks).

How should access to the audio be granted?

 Selected AudioDN Player web component with a Client-Side Player key Fastest setup. Drop in the AudioDN Player web component; it creates and renews play sessions. Suitable when application-specific server approval is not required for every listener. Selected Your browser or native application with a Client-Side Player key The client creates a play session directly. You use a custom web or native player. The key must be appropriately scoped.  Selected Your server creates a play session An API Access key on your server. Your server checks logins, purchases, subscriptions, permissions, or entitlements, then returns a short-lived play session.  Selected Your server creates signed delivery URLs A URL Signing key on your server. Does not create a play session. Suitable when possession of the temporary link is sufficient access.

How should the audio be played?

 Selected Pass the play session to the AudioDN Player web component Your server creates the session; the AudioDN Player web component handles streaming. Selected Use the returned playback resources in a custom web or native player Fetch signed variant URLs and play them in your own media interface.

## AudioDN Player web component with a Client-Side Player key

Fastest setup. Drop in the AudioDN Player web component; it creates and renews play sessions. Suitable when per-listener server approval is not required.

1

#### Create a Client-Side Player key

In the [dashboard](https://account.audiodeliverynetwork.com) create a **Client-Side Player** key. Optionally scope it to a collection, track, and/or variants. This key can only create play sessions — not manage tracks or collections.

2

#### Install the Player web component

```
npm install @audiodn/components
```

```
import '@audiodn/components/player'
```

Or from a CDN:

```
<script type="module" src="https://unpkg.com/@audiodn/components@latest/dist/player.js"></script>
```

3

#### Render the Player web component

```
<audiodn-player
  api-key="CLIENT-SIDE-PLAYER-KEY"
  scope="collection"
  id="COLLECTION-ID"
  variant="hq"
  size="large"
></audiodn-player>
```

Either `api-key` or `play-session-id` is required — never both. See the [Player component](/docs/components/player) reference.