Use the Descript API to automate imports, trigger Underlord edits, and build integrations — without opening the app. For the full endpoint reference with request schemas and code samples, see the API documentation.
Looking to control Descript by chatting with an AI assistant? See Use Descript with an AI assistant (MCP) instead.
Using the API to import media or talk to Underlord will use media minutes and AI credits.
For more info, see Track and understand your media minutes and AI credits.
This article covers:
- What is an API?
- What can I do with the API?
- How to create your API token
- Choose how to use the API
- Known limitations
What is an API?
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.
New to APIs? Here's a glossary of important terms and acronyms.
Glossary of key concepts
API token: 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. Don't share your API token with others. Keep it secret, keep it safe.
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.
What can I do with the API?
Import media into a new project. The API can create a project (with folder support), import media from a URL or via direct file upload from your machine, transcribe it, and set up a composition — all in one step. Import multiple files at once and arrange them into a timeline.
Manage projects. Search and list projects, and get project info (media and compositions).
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.
Export to a Descript share link. Use the API to publish projects and generate shareable web links with configurable access levels. Direct file export endpoints aren't available yet — export manually in Descript for now.
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.
- Go to your Descript account settings and click the API tokens section.
- Click Create token.
- Give your token a name and select the Descript drive it should be tied to. When you're ready, click Create token.
- Copy and store your token 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.
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
Zapier, the command line, direct HTTP, and AI coding tools are all just different ways to talk to the same API.
Example requests
- "Create a Descript project from this video URL"
- "Add Studio Sound and captions to my latest project"
- "Make a 30-second highlight reel from my project"
- "Write a script about how to make great coffee and create a video from it"
Zapier — Connect Descript to your existing workflows
Connect Descript, set your trigger (new file, new recording, new post), and then feed a prompt to Underlord. Best for teams already comfortable with Zapier, or anyone who wants to wire this into existing automation workflows without touching code.
Set up with Zapier
- Create a Zapier account (it's free!) and use this link to gain access to the Descript <> Zapier integration.
- In Zapier, create a new Zap.
- After adding a trigger of your choice, add a new Action step.
- Search for and select the Descript API.
- Choose the event to run. Currently, the options are Import Media and Edit with AI (Underlord).
-
In the Account section, select or connect your Descript account by entering your API token.
Use your own private, personal API token
Use your own API token. Once connected, it will appear as a Personal connection in Zapier.
Do not share this connection with your Zapier organization. Each team member should create their own.
If your Zap uses multiple Descript steps (e.g., Import Media and Edit with AI), select this same connection for each one. Mismatched connections will cause errors.
- Continue configuring the action fields and test the step.
Command line
Install the CLI, drop in your API key, and run imports and edits from your terminal. It handles polling and shows live progress — useful for testing before you build something real. Good for technical users who want to test things quickly.
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.
Claude Code
Connect the Descript MCP to Claude Code (or Codex, or Cursor) to build your own custom integration on top of the API. This gives your vibecoding tool of choice context into the Descript API. See Use Descript with an AI assistant (MCP) for those steps.
Known limitations
Here's what's not yet available:
- No local export endpoint. You can publish projects to Descript web links and get back signed URLs to the mp4, but exporting local files directly via the API without publishing is not yet supported. You'll need to do this manually in Descript for now.
-
Google Drive, Dropbox, and Zapier limitations:
- Zapier: When importing media from Google Drive or Dropbox, select the File field in your action config (not Media URL or DownloadURL). Standard share links and download URLs will return errors. Imported files are limited to 1 GB.
- Direct API: Standard share links won't work because they point to a webpage, not the file itself. Convert them to direct download links before passing them to the API.
- CLI: Use a Google Drive or Dropbox share link directly — the CLI converts it 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.
- 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. 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.