Batch Run Workflow

from extend_ai import Extend, WorkflowReference, FileFromUrl
from extend_ai.workflow_runs import WorkflowRunsCreateBatchRequestInputsItem
client = Extend(
    token="YOUR_TOKEN_HERE",
    extend_api_version="2026-02-09",
)
client.workflow_runs.create_batch(
    workflow=WorkflowReference(
        id="wf_1234567890",
    ),
    inputs=[
        WorkflowRunsCreateBatchRequestInputsItem(
            file=FileFromUrl(
                url="https://example.com/invoice1.pdf",
            ),
            metadata={
                "customerId": "cust_abc123"
            },
        ),
        WorkflowRunsCreateBatchRequestInputsItem(
            file=FileFromUrl(
                url="https://example.com/invoice2.pdf",
            ),
            metadata={
                "customerId": "cust_def456"
            },
        )
    ],
)

{
  "batchId": "batch_zyx987"
}

Unlike the single Run Workflow endpoint which returns the details of the created workflow runs immediately, this batch endpoint returns a batchId.

Our recommended usage pattern is to integrate with Webhooks for consuming results, using the metadata and batchId to match up results to the original inputs in your downstream systems. However, you can integrate in a polling mechanism by using a combination of the List Workflow Runs endpoint to fetch all runs via a batch, and then Get Workflow Run to fetch the full outputs each run.

Priority: All workflow runs created through this batch endpoint are automatically assigned a priority of 90.

Processing and Monitoring: Upon successful submission, the endpoint returns a batchId. The individual workflow runs are then queued for processing.

Monitoring: Track the progress and consume results of individual runs using Webhooks. Subscribe to events like workflow_run.completed, workflow_run.failed, etc. The webhook payload for these events will include the corresponding batchId and the metadata you provided for each input.
Fetching Results: You can also use the List Workflow Runs endpoint and filter using the batchId query param.

This endpoint allows you to efficiently initiate large batches of workflow runs in a single request (up to 1,000 in a single request, but you can queue up multiple batches in rapid succession). It accepts an array of inputs, each containing a file and metadata pair. The primary use case for this endpoint is for doing large bulk runs of >1000 files at a time that can process over the course of a few hours without needing to manage rate limits that would likely occur using the primary run endpoint. Unlike the single [Run Workflow](https://docs.extend.ai/2026-02-09/api-reference/endpoints/workflow/create-workflow-run) endpoint which returns the details of the created workflow runs immediately, this batch endpoint returns a `batchId`. Our recommended usage pattern is to integrate with [Webhooks](https://docs.extend.ai/2026-02-09/webhooks/configuration) for consuming results, using the `metadata` and `batchId` to match up results to the original inputs in your downstream systems. However, you can integrate in a polling mechanism by using a combination of the [List Workflow Runs](https://docs.extend.ai/2026-02-09/api-reference/endpoints/workflow/list-workflow-runs) endpoint to fetch all runs via a batch, and then [Get Workflow Run](https://docs.extend.ai/2026-02-09/api-reference/endpoints/workflow/get-workflow-run) to fetch the full outputs each run. **Priority:** All workflow runs created through this batch endpoint are automatically assigned a priority of 90. **Processing and Monitoring:** Upon successful submission, the endpoint returns a `batchId`. The individual workflow runs are then queued for processing. - **Monitoring:** Track the progress and consume results of individual runs using [Webhooks](https://docs.extend.ai/2026-02-09/webhooks/configuration). Subscribe to events like `workflow_run.completed`, `workflow_run.failed`, etc. The webhook payload for these events will include the corresponding `batchId` and the `metadata` you provided for each input. - **Fetching Results:** You can also use the [List Workflow Runs](https://docs.extend.ai/2026-02-09/api-reference/endpoints/workflow/list-workflow-runs) endpoint and filter using the `batchId` query param.

Authentication

AuthorizationBearer

Bearer authentication of the form Bearer <token>, where token is your auth token.

Request

This endpoint expects an object.

workflowobjectRequired

The workflow to run.

inputslist of objectsRequired

An array of input objects to be processed by the workflow. Each object represents a single workflow run to be created. The array must contain at least 1 input and at most 1000 inputs.

Response

Successfully queued batch workflow run

batchIdstring

A unique identifier for the submitted batch. This ID can be used to correlate the workflow runs created by this request. You can find this batchId associated with individual runs when listing workflow runs or in webhook payloads.

Errors

400

Bad Request Error

401

Unauthorized Error

402

Payment Required Error

403

Forbidden Error

404

Not Found Error

422

Unprocessable Entity Error

429

Too Many Requests Error

500

Internal Server Error

Unlike the single Run Workflow endpoint which returns the details of the created workflow runs immediately, this batch endpoint returns a batchId.

Priority: All workflow runs created through this batch endpoint are automatically assigned a priority of 90.

Processing and Monitoring: Upon successful submission, the endpoint returns a batchId. The individual workflow runs are then queued for processing.

Monitoring: Track the progress and consume results of individual runs using Webhooks. Subscribe to events like workflow_run.completed, workflow_run.failed, etc. The webhook payload for these events will include the corresponding batchId and the metadata you provided for each input.
Fetching Results: You can also use the List Workflow Runs endpoint and filter using the batchId query param.

Batch Run Workflow

Authentication

Headers

Request

Response

Errors

Authentication

Headers

Request

Response

Errors