Submit a human label for a conversation
Attach a supervised label to one of this agent’s conversations — the ground-truth annotation written into the agent’s canonical labeling dataset for eval construction. The conversation is resolved tenant-scoped, the prompt + original answer are derived from its messages (pass input to override), and a corrected response becomes the golden expected_output. Requires the labeler role (owner/admin/developer); 404 when the agent or conversation is unknown, 409 when the dataset hits the per-dataset row ceiling, 422 when no labelable prompt could be derived.
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
Response
{ annotation: {...}, dataset: {...} } — the appended dataset row with the resolved dataset — in the standard { data, meta } envelope.