The Descript Zapier integration ships with built-in actions for Import Media and Edit with AI. To use any other Descript API endpoint from a Zap you'll need to send a direct request with Zapier's API Request action. 

While this guide is specific to Zapier, this method of configuring direct api calls will also work if integrating Descript API into other automation tools for which no Descript integration exists (like n8n or Make).

This article covers:

• How to set up the connection
• How to find the endpoint you need
• How to configure the API Request action
• Response formats: sync vs. async
• Available endpoints and examples

Before getting started

You'll need three things:

1. A Descript API token (create one here)
2. A Zapier account
3. The Descript API documentation open for reference

Step 1: Set up the connection

1. In your Zap, add a new action step.
2. Search for API by Zapier and select it. Note: this is a premium feature, and may not be available on all Zapier plans.
3. Choose API Request as the action event.
4. Click Connect a new account. A configuration window opens.
5. Fill in the fields in the table below.

6. Click Yes, Continue to API by Zapier.

   Field	Value
   Authentication Type	None
   Connection Name	Descript API (or whatever you prefer)
   Domain Filter	descriptapi.com
   Headers (under Static Headers)	Authorization: Bearer YOUR_API_TOKEN on the first line, Content-Type: application/json on the second line
   Query Parameter	Leave empty
   OAuth2	Leave empty

Step 2: Find the endpoint you need

Open the API documentation and find the endpoint you want to use. Each endpoint page lists the three things you'll enter in Zapier:

• The HTTP method — POST, GET, or DELETE. Look for the label next to the endpoint name (for example, "post Export project transcript").
• The URL — shown in each endpoint section, for example https://descriptapi.com/v1/export/transcript.
  
• The request body — the JSON payload the endpoint expects. The docs list every field, whether it's required or optional, and what values it accepts.

Step 3: Configure the API Request action

Depending on the endpoint you're calling, you will need to specify a given set of inputs and values.  Back in Zapier, fill in the action fields:

1. Set the HTTP Method to match the docs (usually POST).
2. Paste the full URL from the docs.
3. In the Body field, enter your JSON payload. Reference data from earlier Zap steps using Zapier's {{field}} syntax — for example, passing a project ID from an earlier Import Media step.

You don't need to add authentication headers here. They're included automatically from the connection you set up earlier.

{
  "project_id": "{{project_id_from_previous_step}}",
  "format": "txt",
  "include_speaker_labels": "changes",
  "include_markers": true,
  "timecodes": {
    "on_paragraphs": true
  }
}

Response formats: sync vs. async

The built-in Descript Zapier actions handle polling and response parsing for you. When calling API Request directly, two patterns matter:

Async endpoints (like Publish) return a job_id in JSON. You'll need a follow-up step to poll GET https://descriptapi.com/v1/jobs/{{job_id}} until the job completes, or pass a callback_url in your request body to have Descript notify a Zapier webhook when the job finishes.

Sync endpoints (like Transcript Export) return the file content directly — not JSON. Zapier's API Request action expects JSON responses, so these may not parse cleanly. If you run into issues, try using a text-based format (like txt or markdown for transcripts) instead of binary formats (like docx), or handle the request in a Code by Zapier step where you have more control over the response.

Available endpoints and examples

For the full list of endpoints, request schemas, and code samples, see the API documentation. Endpoints not covered by the built-in Zapier integration include:

• Export transcript — export a composition's transcript as text, Markdown, HTML, RTF, or DOCX
• List projects — search and filter projects in your drive
• Get project details — inspect a project's media files and compositions

Examples

One example per endpoint, showing all available parameters with realistic values. All examples use POST or GET/DELETE as appropriate.

{
  "project_name": "Q3 Campaign Video",
  "team_access": "comment",
  "folder_name": "Clients/Videos",
  "add_media": {
    "Intro/opener.mp4": {
      "url": "https://storage.example.com/opener.mp4",
      "language": "en"
    },
    "Main/interview.mp4": {
      "url": "https://storage.example.com/interview.mp4",
      "language": "en"
    },
    "Main/broll.mp4": {
      "url": "https://storage.example.com/broll.mp4"
    },
    "Multitrack/session": {
      "tracks": [
        { "media": "Main/interview.mp4", "offset": 0 },
        { "media": "Main/broll.mp4", "offset": 12.5 }
      ]
    }
  },
  "add_compositions": [
    {
      "name": "Rough Cut",
      "fps": 30,
      "width": 1920,
      "height": 1080,
      "clips": [
        { "media": "Intro/opener.mp4" },
        { "media": "Multitrack/session" }
      ]
    }
  ],
  "callback_url": "INSERT ZAPIER CALLBACK URL HERE"
}

{
  "project_id": "YOUR_PROJECT_ID",
  "composition_id": "YOUR_COMPOSITION_ID",
  "prompt": "Remove all filler words, apply Studio Sound to every clip, add captions, and create a 60-second highlight reel as a separate composition",
  "team_access": "view",
  "conversation_id": "d1e2f3a4-b5c6-7890-abcd-ef1234567890",
  "callback_url": "INSERT ZAPIER CALLBACK URL HERE"
}

{
  "project_id": "YOUR_PROJECT_ID",
  "composition_id": "YOUR_COMPOSITION_ID",
  "media_type": "Video",
  "resolution": "1080p",
  "access_level": "unlisted",
  "callback_url": "INSERT ZAPIER CALLBACK URL HERE"
}

{
  "project_id": "YOUR_PROJECT_ID",
  "composition_id": "YOUR_COMPOSITION_ID",
  "format": "markdown",
  "include_speaker_labels": "every_paragraph",
  "include_markers": true,
  "timecodes": {
    "on_paragraphs": true
  }
}