# Trigger Single Test Plan

This endpoint triggers the execution of a single Test Plan programmatically. It is designed for CI/CD pipelines, scheduled regression jobs, or any workflow requiring automated, repeatable test execution.\
Upon invocation, Drizz provisions the required device environment, initiates the Test Plan, and returns a unique `runId` that can be used to track real-time progress, retrieve logs, and access execution artifacts. 

**Endpoint :**\
POST /testplan/run

**Request Headers**

| Header       | Value            |
| ------------ | ---------------- |
| x-api-key    | Access Token     |
| Content-Type | application/json |

**Request Payload Attributes**

| Attribute      | Data Type | Max Length | Description                 | Example                |
| -------------- | --------- | ---------- | --------------------------- | ---------------------- |
| test\_plan\_id | string    | 64         | Unique test plan identifier | ADuF4ViN               |
| apks           | object    | —          | Package-to-version mapping  | { "com.app": "1.0.0" } |

**Response Attributes**

| Attribute                        | Data Type | Description          | Example      |
| -------------------------------- | --------- | -------------------- | ------------ |
| test\_plan\_id                   | string    | Test plan identifier | ADuF4ViN     |
| execution\_details.status        | string    | Execution state      | triggered    |
| execution\_details.execution\_id | string    | Execution identifier | exec\_123456 |


---

# 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-single-test-plan.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.