Batch API

The Batch API is available for Enterprise customers after Exa enables it for your team. Contact sales@exa.ai to discuss Enterprise access and enablement.

The Batch API lets you submit many Exa API requests at once and retrieve their results later as a JSONL file. Instead of sending thousands of individual requests and managing rate limits and retries yourself, you send a single batch, poll its status, and download all the results in one file. Use it for offline enrichment, backfills, or any other job that does not need an immediate response. Full request and response schemas are in the API reference.

The Batch API is in beta. Include the Exa-Beta: batches-2026-06-06 header on every request.

Supported requests

Each batch item must be a POST request to one of these routes:

Route	Use case
`/search`	Run Exa search requests asynchronously
`/agent/runs`	Run Exa Agent requests asynchronously

Each item needs a batch-unique customId. The same customId is returned in the results file so you can map output rows back to your input data.

Create a batch

curl -s -X POST "https://api.exa.ai/batches" \
  -H "Authorization: Bearer $EXA_API_KEY" \
  -H "Exa-Beta: batches-2026-06-06" \
  -H "Content-Type: application/json" \
  -d '{
    "requests": [
      {
        "customId": "row-1",
        "method": "POST",
        "url": "/search",
        "body": {
          "query": "Latest AI infrastructure funding rounds"
        }
      },
      {
        "customId": "row-2",
        "method": "POST",
        "url": "/agent/runs",
        "body": {
          "query": "Summarize recent vector database launches"
        }
      }
    ],
    "metadata": {
      "project": "weekly-digest"
    }
  }' | jq

The response contains the batch ID and initial status:

Example response

{
  "id": "batch_01j7x9v0m2n4p6q8r0s2t4v6w8",
  "object": "batch",
  "status": "in_progress",
  "requestCounts": {
    "total": 2,
    "completed": 0,
    "failed": 0
  },
  "createdAt": "2026-06-06T12:00:00.000Z",
  "expiresAt": null,
  "endedAt": null,
  "resultsUrl": null,
  "metadata": {
    "project": "weekly-digest"
  }
}

Check status

Poll the batch until it reaches a terminal status:

curl -s "https://api.exa.ai/batches/batch_01j7x9v0m2n4p6q8r0s2t4v6w8" \
  -H "Authorization: Bearer $EXA_API_KEY" \
  -H "Exa-Beta: batches-2026-06-06" | jq

Batch statuses are:

Status	Meaning
`in_progress`	The batch is running
`completed`	All requests have finished and results are available
`cancelling`	Cancellation was requested and in-flight work is draining
`cancelled`	The batch was cancelled
`expired`	Results are no longer available

When the batch completes, resultsUrl contains a download URL for the JSONL results file, and expiresAt is set to the end of the results retention window.

resultsUrl is a short-lived presigned URL. Re-fetch the batch to get a fresh URL whenever you need to download results again.

List batches

curl -s "https://api.exa.ai/batches?limit=100" \
  -H "Authorization: Bearer $EXA_API_KEY" \
  -H "Exa-Beta: batches-2026-06-06" | jq

The response is cursor-paginated: data holds up to limit batches, and when hasMore is true, pass nextCursor as the cursor query parameter to fetch the next page. Pass status=completed to list only completed batches:

curl -s "https://api.exa.ai/batches?status=completed" \
  -H "Authorization: Bearer $EXA_API_KEY" \
  -H "Exa-Beta: batches-2026-06-06" | jq

completed is the only supported value; any other value returns an error. Completed listings are ordered by expiry and use their own cursor, so keep sending status=completed on every page — completed and unfiltered cursors are not interchangeable.

{
  "object": "list",
  "data": [],
  "hasMore": false,
  "nextCursor": null
}

Download results

curl "$RESULTS_URL" -o results.jsonl

Each JSONL line contains the original customId and either a response or an error:

{ "customId": "row-1", "response": { "statusCode": 200, "body": { "results": [] } } }
{ "customId": "row-2", "error": { "code": "API_ERROR", "message": "request failed" } }

Cancel a batch

curl -X POST "https://api.exa.ai/batches/batch_01j7x9v0m2n4p6q8r0s2t4v6w8/cancel" \
  -H "Authorization: Bearer $EXA_API_KEY" \
  -H "Exa-Beta: batches-2026-06-06"

Delete a batch

curl -X DELETE "https://api.exa.ai/batches/batch_01j7x9v0m2n4p6q8r0s2t4v6w8" \
  -H "Authorization: Bearer $EXA_API_KEY" \
  -H "Exa-Beta: batches-2026-06-06"

Access

To enable the Batch API for a team, contact sales@exa.ai.

API

Data

MCP

SDKs

Integrations

Agentic payments

Admin

Additional Resources

Batch API

Supported requests

Create a batch

Check status

List batches

Download results

Cancel a batch

Delete a batch

Access

​Supported requests

​Create a batch

​Check status

​List batches

​Download results

​Cancel a batch

​Delete a batch

​Access

Supported requests

Create a batch

Check status

List batches

Download results

Cancel a batch

Delete a batch

Access