Acknowledge a circuit breaker

POST

/api/workspaces/{workspaceId}/quality/circuit-breakers/{id}/acknowledge

• Production

Acknowledge a circuit breaker to indicate a human is aware of the quality issue and investigating. The user ID is extracted automatically from the authentication token.

Authorizations

• bearerAuth

Parameters

Path Parameters

workspaceId

required

string format: uuid

The workspace the circuit breaker belongs to.

id

required

string

The unique identifier of the circuit breaker.

Responses

200

The circuit breaker was acknowledged.

A circuit breaker that pauses the AI pipeline when quality drops below configured thresholds.

object

id

required

Unique identifier for the circuit breaker.

string

Example

cb_11223344-5566-7788-99aa-bbccddeeff00

scopeKey

required

The scope affected by this circuit breaker (e.g., account:accountId).

string

Example

account:acc_12345678-abcd-ef01-2345-678901234567

reason

required

Human-readable explanation of why the circuit breaker was triggered.

string

Example

3 consecutive conversations scored below composite threshold (3.0) for account Example Company

triggeredAt

required

Timestamp when the circuit breaker was triggered.

string format: date-time

Example

2026-03-15T10:00:00.000Z

acknowledgedBy

User ID of the person who acknowledged this circuit breaker.

string | null

acknowledgedAt

Timestamp when the circuit breaker was acknowledged.

string | null format: date-time

resolvedAt

Timestamp when the circuit breaker was resolved.

string | null format: date-time

404

No circuit breaker exists with the given ID.

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"
]