Launch Sale: Creator and Business plans are discounted for a limited time. View pricing

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 →

Playing and accessing tracks

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

Open the playback guide →

Before you integrate

  1. Configure the variants AudioDN should create from each upload.
  2. Create a collection 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.

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 and 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.