> ## Documentation Index
> Fetch the complete documentation index at: https://docs.effectiveai.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Triage objections

> Get a recommendation for each open objection item before preparing a response.

Triage analyzes the existing open items on an objection linked to a managed filing.
Each item gets a separate agent under the filing Captain. The agent reads the
regulator's request, filing evidence, and existing discussion, then recommends a
response and identifies proposed changes or missing information.

Recommendations are saved as comments on the objection items. Triage does not edit
documents, answer the objection, or submit anything to SERFF. Creating items from
an objection letter and asking Captain to implement recommendations are separate
steps.

## Start triage

Use an API key belonging to a member with edit access to the filing and objection,
permission to create sessions, and available spending allowance. Reference filings
cannot be triaged until they are managed filings.

```http theme={null}
POST /api/v2/objections/65773dc2-a473-4f88-b3d4-a37c1860d487/triage
Authorization: Bearer $EFFECTIVE_API_KEY
Content-Type: application/json

{
  "requestId": "4f991ddd-34a1-46cf-ad71-39e1e5bbf296"
}
```

Generate a UUID for each deliberate run. Reuse it when retrying a timed-out or
failed HTTP request. The same objection and request ID identify the same run while
its workflow history is retained. A new request ID starts a new analysis and may
add another recommendation to each item's discussion.

```http theme={null}
HTTP/1.1 202 Accepted
Location: /api/v2/objections/65773dc2-a473-4f88-b3d4-a37c1860d487/triage/4f991ddd-34a1-46cf-ad71-39e1e5bbf296
```

```json theme={null}
{
  "id": "4f991ddd-34a1-46cf-ad71-39e1e5bbf296",
  "objectionId": "65773dc2-a473-4f88-b3d4-a37c1860d487",
  "statusUrl": "/api/v2/objections/65773dc2-a473-4f88-b3d4-a37c1860d487/triage/4f991ddd-34a1-46cf-ad71-39e1e5bbf296"
}
```

Acceptance means the work was queued. Poll the `Location` URL to learn whether it
completed. Missing open items, unavailable documents, or lost permissions can fail
the run after acceptance.

## Read progress and recommendations

```http theme={null}
GET /api/v2/objections/65773dc2-a473-4f88-b3d4-a37c1860d487/triage/4f991ddd-34a1-46cf-ad71-39e1e5bbf296
Authorization: Bearer $EFFECTIVE_API_KEY
```

The response contains `status`, `captainSessionId`, `error`, and an `items` array.
Each item includes `itemId`, `seq`, `status`, `agentSessionId`, `threadId`,
`commentId`, and `error`. IDs are `null` until the corresponding resource exists.
Run and item statuses are `queued`, `running`, `completed`, or `failed`. These are
execution statuses; the objection item's business status remains unchanged.

One item failing does not prevent the other items from completing. A run with any
failed item reports `failed`; successful items still retain their comment IDs.
Read those threads through the [Records comments API](/api-reference).

If an error says publication was not confirmed, inspect the item's existing
comments before starting another run: a comment may have been saved before the
acknowledgement was lost. Publication is not automatically retried.

Progress is available while workflow history is retained. Published comments and
agent sessions follow their normal product retention.

## Scope and limits

Triage captures up to 100 open items and 100 objection documents. Filing capture
supports 500 items and 1,000 document references, with a total metadata limit of
768 KiB and a 64 KiB limit for each item’s agent task. Document references use captured versions. Items added after capture
require a new run. Up to five item agents run concurrently per triage; shared
agent capacity can make items wait.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.