Skip to main content
POST
Add Flag

Overview

Flags pinpoint where on a call something went wrong. The call_id must already be attached as a resource on this issue, otherwise the request fails with 409 conflict and { error: "call_not_attached" }. Flag types accumulate into a reusable per-org catalog (see List Flag Types).

Headers

string
required
Your API key for authentication.

Path Parameters

string
required
Internal UUID of the issue.

Body Parameters

string
required
ID of the attached call this flag points at. Must already be attached as a resource on this issue.
string
required
Flag type. Free-form, but normalized to lower_snake_case before storage. Reusing a type increments its usage_count in List Flag Types.
string
Free-text note explaining why this moment was flagged. 1-4000 characters.
string
ID of the pathway node the flag is attached to, if known.
string
Display name of the pathway node, captured at flag time so the dashboard can render the node name even if the pathway later changes.
integer
Zero-based index of the message turn in the call transcript that this flag points at.
string
Verbatim text of the flagged message, captured at flag time.

Response

Returns 201 Created with the new flag.
object
null | array
null on success.

Docs for agents: llms.txt