> ## Documentation Index
> Fetch the complete documentation index at: https://usenaive.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Ack Relayed Delivery

> Device-token authenticated. The box confirms it accepted (or failed) a relayed trigger delivery.

Once the box's local runtime accepts a relayed `trigger.wake`, it POSTs here to
flip the control-plane delivery from `relayed` to `processed` (or `failed`), so
the delivery-status feed reflects what actually happened on the box.
Device-token authenticated, scoped to the device's company, idempotent.

### Path Parameters

| Parameter | Type   | Description                                       |
| --------- | ------ | ------------------------------------------------- |
| `id`      | string | The trigger delivery id carried in the wake event |

### Request Body

| Parameter | Type   | Required | Description                                  |
| --------- | ------ | -------- | -------------------------------------------- |
| `run_id`  | string | No       | The local agent run id started for this wake |
| `status`  | string | No       | `processed` (default) or `failed`            |
| `error`   | string | No       | Failure detail when `status = failed`        |

<RequestExample>
  ```bash theme={"theme":"css-variables"}
  curl -X POST https://api.usenaive.ai/v1/devices/self/deliveries/td_01H.../ack \
    -H "Authorization: Bearer <device_token>" \
    -H "Content-Type: application/json" \
    -d '{ "run_id": "run_01H...", "status": "processed" }'
  ```
</RequestExample>

<ResponseExample>
  ```json 200 theme={"theme":"css-variables"}
  { "ok": true, "status": "processed" }
  ```
</ResponseExample>

See [delivery status](/docs/api-reference/events/delivery-status) for the full
lifecycle.