Integrations

Pick the approach that fits your product. Approaches are composable — upload with a web component, create play sessions on your server, play with the AudioDN Player, and receive processing events through webhooks.

Upload and playback are independent

Decide how you upload and how you play separately. A Client-Side Upload key never replaces a Player key, and an API Access key stays on your server.

Web Components

Ready-made Uploader, Recorder, Player, and Waveform UI without building your own media chrome.

Open overview →

REST API

Full control from web, mobile, and server apps — custom UIs, native players, and backend workflows.

Open overview →

AI & MCP

Connect an AI coding assistant to AudioDN documentation and supported live operations while you build.

Open MCP docs →

Webhooks

Receive notifications when tracks become playable, outputs finish, or collections change.

Open overview →

Dashboard / no-code

Upload, organize, and manage tracks in the account dashboard without writing integration code. Use the dashboard alone, or alongside components and the API.

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.
  • 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 API Keys and Signing Keys.

Before you integrate

  1. Configure the output presets AudioDN should create from each upload (see also the Output Presets API).
  2. Create a collection to organize tracks.
  3. Choose credentials in the dashboard for the flows you will use.

Task guides: Uploading audio, Playback & delivery, Voice & transcription. Component and API details stay in the reference sections.