Descript API (beta)

The Descript API (application programming interface) is how you connect Descript to your existing tools and workflows without opening the Descript app. Automate editing tasks, batch-process recordings, build custom integrations, and use AI assistants to create and edit projects on your behalf.

This article covers:

Descript API overview interface

What can I do with the API?

Import media into a new project. The API can create a project, import media from a URL, transcribe it, and set up a composition — all in one step. Import multiple files at once and arrange them into a timeline.

Edit with Underlord. Anything Underlord can do in the app, it can do through the API — add Studio Sound, remove filler words, create highlight clips, add captions, generate B-roll, translate audio, and more. It can also create an entirely new project from just a prompt, no media needed. If you can describe it, Underlord can do it.

If you're connecting through an AI assistant like Claude, the connector handles this through your Descript login — no token needed. For everything else (the terminal or Zapier), you'll need to create one.

What about exporting?

Publishing and export endpoints aren't available just yet — you'll need to do this manually in Descript for now. Stay tuned!

How it works

Think of the API as a waiter at a Descript restaurant. You place your order, the waiter takes it to the kitchen, and when your food is ready, the waiter brings it back to you. The API works the same way — you send a request, Descript processes it in the background, and then gives it to your waiter, who brings it directly to you.

Before you can order though, the waiter needs to know you're actually a customer. That's what your API token is for — think of it as your access badge. It proves the request is coming from you and tells Descript which drive to work with. Without a valid token, the API won't accept your requests.

Key concepts

New to APIs? We have a glossary of important terms and acronyms

Glossary of key concepts

API token. This is a unique key that authenticates your requests — like a password that lets your tools talk to Descript. Each token is tied to a specific drive. These are super valuable. Don’t share your API token with others! Keep it secret, keep it safe.

Drive. Where your projects, media, and settings live in Descript. Your API token is scoped to one drive, so if you work across multiple drives, you'll need a separate token for each.

Job. Any long-running operation (importing media, running an agent edit). Each job has an ID and a status you can check.

Media minutes and AI credits. Importing and processing media consumes media minutes from your plan. Underlord edits consume AI credits. If you run out of either, requests will return a 402 error.

Projects and compositions. A container for your content in Descript. When you import media through the API, it creates a new project. A project can have multiple compositions — for example, a rough cut and a final version. When importing, you can specify how clips are arranged in a composition. Learn more about projects and compositions.

How to create your API token

Your API key authenticates your requests and connects them to a specific Descript drive. Each token is tied to one drive, so if you work across multiple drives, you'll need a separate key for each.

  1. Go to your Descript account settings and click the API tokens section.
  2. Click Create token.
    Create API token button
  3. Give your token a name and select the Descript drive it should be tied to. When you're ready, click Create token.
    Name and assign API token
  4. A window will appear with your token. Copy and store it in a safe place — you won't be able to view it again. If you lose it, you'll need to generate a new one.
    API token generated modal

Keep your token private

Anyone with your token can make API requests on your behalf, consuming your media minutes and AI credits. Keep it secret; keep it safe!

Choose how to use the API

The API is what powers everything below — whether you're writing code, connecting Zapier, or chatting with an AI assistant. These are just different ways to talk to it.

Pick the path that matches what you're trying to do:

MCP

Use Descript through Claude, GPT, or other AI tools.

Best for: Using Descript through conversation. No code required.

The Descript API supports MCP (Model Context Protocol), which lets AI assistants like Claude use Descript on your behalf. Instead of writing code or building automations, you work through conversation — ask the assistant to create a project, import a video, or edit with Underlord.

Automation tools (Zapier)

Connect Descript to other apps. Best for automating repeatable workflows. No code required.

Set up with Zapier

Before you begin: You must sign up for access to the Descript API and Zapier integration. Visit descript.com/enterprise/api-early-access to request access.

  1. Create a Zapier account (it’s free!) and install the Descript app. Use THIS LINK to accept the Descript Zapier invitation.
    Install Descript Zapier app

     

  2. In Zapier, create a new Zap.
    Create Zap

     

  3. After adding a trigger of your choice, add a new Action step.
    Add Zapier action step

     

  4. Search for and select the Descript app.
    Select Descript app in Zapier

     

  5. Choose the event you want to run, such as Import Media.
    Choose Zapier event

     

  6. Continue configuring the action fields and test the step.
    Configure Zapier action

     

Command line (CLI)

Install the CLI, drop in your API key, and run imports and edits from your terminal. It handles the polling and shows live progress — useful for testing before you build something real. Good for technical users who want to test things quickly.

Set up the CLI

Direct API

Call the API directly over HTTP. You own the logic — job orchestration, error handling, webhooks, the whole thing. Good for: Engineering teams standing up production workflows.

The Read the API documentation

 

Known limitations

Here's what's not yet available:

  • No publish or export endpoint. Open your project in Descript to export.
  • Google Drive and Dropbox links require extra steps. If you're using the API directly (or Zapier), standard share links won't work because they point to a webpage, not the file itself. You'll need a direct download link instead.
    • If you're using the CLI, you can use a Google Drive or Dropbox share link directly — the CLI will convert the share link to a direct download link automatically. Make sure the file is set to "Anyone with the link can view." Very large files may not work due to Google's virus scan blocking the download.
  • No uploading from your computer. You can't drag-and-drop or browse for a file on your computer to send it through the API. Your video or audio needs to already be hosted somewhere online (like Google Drive, Dropbox, or another cloud storage service) so the API can pull it in using a link.
  • No composition-level targeting for agent edits yet. The composition_id parameter is accepted but not yet functional.
  • Tokens are scoped to a single drive. You'll need separate tokens for each drive. Editing a project on a different drive than your token is scoped to will return a 403 error, even if you have permissions on that project.
  • Job history is only available for 30 days. You can look up any import or edit job for up to 30 days after it ran. After that, it's no longer accessible — so if you need to keep records, save your job details as you go.

For updates and discussion, join the Descript API Discord.