Ack Relayed Delivery

POST

devices

self

deliveries

{id}

ack

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" }'

{ "ok": true, "status": "processed" }

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`

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" }'

{ "ok": true, "status": "processed" }

See delivery status for the full lifecycle.

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" }'

{ "ok": true, "status": "processed" }

Overview

Endpoints

Ack Relayed Delivery

Path Parameters

Request Body

​Path Parameters

​Request Body

Path Parameters

Request Body