Tagging and labeling conversations
Tagging and labeling conversations
POST Add tags to a conversation — Adds one or more tags to a conversation and returns the updated tag list.GET List all unique tags used by the organization — Returns the distinct tag names used in conversations for the organization, together with any saved color definitions for tag picker and autocomplete UIs.GET List tags for a conversation — Returns the current tag list for one conversation in the current organization. The conversation must exist and not be soft-deleted, otherwise a 404 is returned.DELETE Remove a tag from a conversation — Removes one tag from a conversation and returns a standard delete success response. The route requires admin access.Was this page helpful?
Update a conversation
Updates mutable conversation fields such as status, priority, assigned operator, and metadata. Operator access is required. If `expectedVersion` is provided, the request uses optimistic locking and returns a conflict when the stored version has changed since the client last read it. Authenticate with an organization API key sent in `X-API-Key` or as a Bearer token and carrying the exact `conversations:write` scope. API-key access also requires the Automation & API module (`automation_api`). Authorized dashboard sessions remain supported where the route already permits them. The request is isolated to the authenticated organization. Resource and site/project identifiers must belong to that organization; out-of-scope identifiers are not disclosed. When a version is supplied, stale updates fail with a conflict instead of overwriting a newer change. Successful mutations invalidate cached lists and publish the route's documented realtime and webhook events. Retry behavior: Repeating the same request converges on the same resource state, but a retry may return a conflict or not-found response after the first request succeeds.
Add tags to a conversation
Adds one or more tags to a conversation and returns the updated tag list. Duplicate tag names are ignored, so sending the same tag more than once has no extra effect.