> For the complete documentation index, see [llms.txt](https://docs.drizz.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.drizz.dev/automate-and-integrate.md).

# Automate & integrate

- [API Overview](https://docs.drizz.dev/automate-and-integrate/api-overview.md): The Drizz REST API in one page — the auth model, the 24-hour token, rate limits, and the three calls that get a build running.
- [Authenticate](https://docs.drizz.dev/automate-and-integrate/authenticate.md): Exchange client credentials for a Drizz access token and send it on every API call. Tokens are valid for 24 hours.
- [Upload a build](https://docs.drizz.dev/automate-and-integrate/upload-a-build.md): Upload an app binary to Drizz over the API so test plans can run against it. Multipart form, one file, 500 MB cap.
- [Trigger a run](https://docs.drizz.dev/automate-and-integrate/trigger-a-run.md): Start one test plan or a batch over the API. Returns an execution\_id and nothing else — there is no status endpoint.
- [Errors & limits](https://docs.drizz.dev/automate-and-integrate/errors-and-limits.md): Every status code the Drizz API returns, what each common failure means, and the rate limits to design around.
- [CI/CD](https://docs.drizz.dev/automate-and-integrate/ci-cd.md): Trigger Drizz test plans from GitHub Actions, Jenkins, GitLab CI and others — and what a pipeline cannot do yet.
- [Jira](https://docs.drizz.dev/automate-and-integrate/jira.md): Create Jira issues from failed Drizz tests, and the shared-token attribution caveat that applies to every generated ticket.