---
title: "Trigger a directive run"
method: POST
path: "/robots/v0/directives/{DIRECTIVE_ID}/runs"
tags: ["Directives (v0)"]
deprecated: true
---

# Trigger a directive run

`POST /robots/v0/directives/{DIRECTIVE_ID}/runs`

## Request

- Base URL: `https://api.mux.com`
- URL: `https://api.mux.com/robots/v0/directives/{DIRECTIVE_ID}/runs`
- Auth: one of:
  - HTTP basic
  - HTTP bearer

> **Deprecated.**

Deprecated: use `POST /robots/v1/directives/{directive_id}/runs` instead. Starts a directive run against a specific Mux asset. The directive engine dispatches the configured workflows and tracks the run to terminal.

## Path parameters

- `DIRECTIVE_ID` string, required: Directive ID returned by directive creation or listing (drv_...).

## Request body

- RunDirectiveRequestV0
  - `asset_id` string, required: The bare Mux asset ID to run the directive against, as returned by the Mux Video API.

## Response `202`

Directive run started

- DirectiveRunResponseV0
  - `data` DirectiveRunV0, required
    - `run_id` string, required: Unique run identifier (drvrun_...).
    - `subject_id` string, required: The bare Mux asset ID the directive is running against.
    - `status` 'pending', required: The run has been queued.

## Other responses

- `400`: Malformed or missing JSON request body
- `401`: Missing or invalid Mux credentials
- `403`: Robots is not enabled for this environment, or a free-plan workflow or unit limit prevents the directive run
- `404`: Directive not found
- `409`: A run for this directive is already in progress
- `422`: Asset validation failed
- `500`: Server error

## Changes

- **2026-10-26** `151835caff06`: 1 info
  - endpoint deprecated
- **2026-10-19** `7e2e5079412d`: 3 info
  - api operation id `run-directive` removed and replaced with `run-directive-v0`
  - api tag `Directives (v0)` added
  - api tag `Directives` removed
- **2026-10-08** `296f0b01bb84`: 1 breaking, 13 info
  - request body became required
  - added the non-success response with the status `400`
  - added the optional property `error/messages` to the response with the `401` status
  - added the optional property `error/messages` to the response with the `403` status
  - …10 more
- **2026-08-12** `5b4b3133f27d`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/muxinc/apis/mux-api/changes/robots/v0/directives/:DIRECTIVE_ID/runs/post.md)

---

[API](https://skmtc.dev/muxinc/apis/mux-api.md) - [All operations](https://skmtc.dev/muxinc/apis/mux-api/llms.txt) - [OpenAPI document](https://skmtc.dev/muxinc/apis/mux-api/revisions/75b4251a1d96?raw)
