# Trigger Multiple Test Plans (Batch)

This endpoint allows triggering multiple Test Plans in a single API request. It is built for large-scale regression suites, nightly automation pipelines, and orchestrated CI/CD workflows where several Test Plans must run together or in controlled batches.\
Drizz executes each Test Plan independently, provisions devices as required, and returns a consolidated batch `runId` along with individual run references. This ensures predictable, parallel, and fully auditable multi-plan execution.

Endpoint\
POST /testplan/run/batch

**Request Payload Attributes**

| Attribute                     | Data Type | Max Length | Description               | Example                |
| ----------------------------- | --------- | ---------- | ------------------------- | ---------------------- |
| test\_plans                   | array     | —          | List of test plan objects | \[]                    |
| test\_plans\[].test\_plan\_id | string    | 64         | Test plan ID              | nBZfQL3R               |
| test\_plans\[].apks           | object    | —          | APK version mapping       | { "com.app": "1.0.0" } |

**Response Attributes**

| Attribute              | Data Type | Description            | Example                |
| ---------------------- | --------- | ---------------------- | ---------------------- |
| message                | string    | Batch execution status | Triggered successfully |
| successful\_executions | array     | Successful runs        | \[]                    |
| failed\_executions     | array     | Failed runs            | \[]                    |


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.drizz.dev/drizz-api-integration/trigger-run/trigger-multiple-test-plans-batch.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.