# Integrations | AudioDN Docs

> Upload tracks and play or access audio as two independent tasks — choose credentials, components, or custom interfaces one decision at a time.

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

---

# Integrations

AudioDN integrations are two independent tasks: **uploading tracks** and **playing and accessing tracks**. You do not need to pick a single architecture labeled Web, Mobile, Hybrid, Server-Side, or Signed Delivery.

#### Upload and playback are independent

A product can upload with the AudioDN Uploader web component and a Client-Side Upload key, then create gated play sessions on the server and pass them to the AudioDN Player web component — or any other combination.

[

## Uploading tracks

Who creates the upload session, and whether you use the AudioDN Uploader or (voice) Recorder web components or a custom interface.

Open the uploading guide →

](/docs/integration/uploading)[

## Playing and accessing tracks

Client-Side Player keys, server-created play sessions, or signed delivery without a play session.

Open the playback guide →

](/docs/integration/playback)

### Before you integrate

1.  Configure the [variants](/docs/variant-types) AudioDN should create from each upload.
2.  Create a [collection](/docs/api/collections) to organize tracks.
3.  Choose credentials in the dashboard: Client-Side Upload, Client-Side Player, API Access, or URL Signing — depending on your flow.

Prefer a non-technical walkthrough first? Start on [Get Started](/get-started).

### Credentials at a glance

-   **Client-Side Upload key** — browser or native app; creates upload sessions only.
-   **Client-Side Player key** — browser or native app; creates play sessions only (cannot manage tracks or collections).
-   **API Access key** — server only; full API including session creation and catalog management.
-   **URL Signing key** — server only; signs delivery URLs without creating a play session.

See the [API Keys](/docs/api/api-keys) and [Signing Keys](/docs/api/signing-keys) references.

Components and the full API reference remain separate sections in the sidebar. AI tools (MCP, Agent Kit, AI Plugin) help implement these same two flows — they are not additional integration paths.