# Error Code

This section outlines the HTTP status codes returned by Drizz Public APIs. Each code reflects the state of the request ranging from successful triggers to validation issues, conflicts, or service-level errors.These responses enable engineering, QA, and CI/CD systems to programmatically detect failures, apply retries, escalate integration issues, and maintain predictable automation workflows.

####  HTTP Status Codes

| Code | Description  | Action                               |
| ---- | ------------ | ------------------------------------ |
| 200  | Success      | Execution triggered successfully     |
| 207  | Multi-Status | Inspect failed executions            |
| 400  | Bad Request  | Validate payload and parameters      |
| 404  | Not Found    | Verify test plan or app registration |
| 409  | Conflict     | APK version already exists           |
| 500  | Server Error | Contact Drizz support                |
| 502  | Bad Gateway  | Retry or check service availability  |


---

# 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/error-code.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.