Submit a reply for supervisor approval
Submit a proposed reply for a conversation through the reply-approval gate. When the sending operator is gated (a per-agent override or the org default requires approval) the reply is held as pending for a supervisor and gated=true is returned; when they are not gated — or are the workspace owner, who is never gated — it dispatches immediately through the standard reply path and gated=false is returned. Use this as the outbound reply path on teams that require supervisor sign-off.
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 Response
Reply accepted: either queued for approval (gated=true) or dispatched directly (gated=false).
Reply accepted: either queued for approval (gated=true) or dispatched directly (gated=false).