Send a supervisor note to a live conversation
Post a one-way supervisor note (1-1000 characters) onto a live agent conversation. The agent consumes the note on its next turn, so the conversation must still be active, open, or escalated — a closed conversation returns 404. The author id is taken from the authenticated session, never from the body, and every note is audit-logged.
Authorizations
Dashboard JWT token from Clerk
Headers
Stripe-style idempotency token. Pass a stable, client-generated value (1-255 chars) to dedupe retries on transient timeouts. The same key+credential+path replays the original response for 24h on 2xx (5min on 4xx, 30s on 5xx). Returns 409 if a concurrent request with the same key is already in flight; replayed responses include the Idempotency-Replay: true response header.
1 - 255Sandbox opt-in for Clerk-session-authenticated requests. Set to true to route the call through the test-mode pipeline: no real provider delivery, no credits deducted, response meta.test_mode: true. Ignored for live API keys (dv_live_sk_*) — server-to-server clients must use a test-prefixed key (dv_test_sk_*) to exercise sandbox. Test-prefixed keys unconditionally enable sandbox regardless of this header.
true, false Path Parameters
The agent conversation id.
1 - 200Body
The note to send — the agent reads it on its next turn.
The note to send — the agent reads it on its next turn.
The note text the agent consumes on its next turn.
1 - 1000