Resolve an attention item

POST

/api/attention-items/{id}/resolve

• Production

Marks an attention item as resolved, indicating that a human has reviewed and addressed the flagged issue. This does not affect the underlying conversation — use the conversation endpoints to take over, reply, or resolve the conversation itself.

Authorizations

• bearerAuth

Parameters

Path Parameters

id

required

string format: uuid

The unique identifier of the attention item to resolve.

Request Body

object

reason

Why the item is resolved, kept with it.

string

>= 1 characters

Example

Handled by phone with the customer.

Responses

200

The attention item has been marked as resolved.

Simple success acknowledgment returned by action endpoints (reply, resolve, take-over, etc.).

object

ok

required

Always true on success.

boolean

Example

true

404

The id is not an attention item id (Attention item not found). An item that is no longer open, or that does not exist in your account, is left as it is and the call answers 200.

Standard error response returned by all endpoints on failure.

object

error

required

A human-readable error message describing what went wrong.

string

Example

Conversation not found

code

A machine-readable reason on some refusals, for example ‘key_lock’ when an API key’s brand or workspace restriction does not cover the action.

string

Example

key_lock

missing_scopes

On a 403 for an API key without a scope the endpoint requires: the scopes the key lacks.

Array<string>

Example

[
  "mcp:write"
]

entryId

On a 409 with code duplicate_question or duplicate_rule_text: the knowledge base entry or policy that already holds the question or rule text.

string format: uuid

Example

11223344-5566-4788-99aa-bbccddeeff00

connectionId

On a 422 about one MCP connection a request names, from an assignment or an agent create or update (a connection that does not exist, one listed twice, or one that does not declare a tool named): the connection, as the request named it.

string

undeclaredTools

On the same 422: the tool names the connection does not declare.

Array<string>

Example

[
  "get_orders"
]

declaredTools

On the same 422: the tools the connection declares.

Array<string>

Example

[
  "get_order",
  "search_orders"
]