For AI agents: a documentation index is available at the root level at /llms.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
<Badge>Available by Request</Badge>
The core agent write. Post one finding per slot, evaluated against the slot's `criteria`, reporting one `outcome`. The outcome is the slot transition: `APPROVE` → `APPROVED_BY_CORA` · `REQUEST_REPLACEMENT` → `WAITING_ON_APPLICANT` / `REPLACEMENT_REQUESTED` · `REQUEST_CORRECTION` → `CORRECTION_IN_PROGRESS` · `ROUTE_TO_COMPLIANCE` → `NEEDS_COMPLIANCE_REVIEW`.
Agents have no status PATCH: `IN_REVIEW` is set by Fortress when it dispatches `requirement.upload_received`; the finding is the only way out. Fortress publishes the matching `requirement.*` event (echo-suppressed for the agent that wrote it).
400 — missing or mismatched `reasonCode`, finding against a `FORM` slot. 409 — stale `requirementVersion`, slot already `APPROVED_BY_COMPLIANCE`, household paused.
<Note>
This endpoint is part of the document-review agent surface. To explore availability for your integration, please contact our team.
</Note>
Path parameters
applicationIdstringRequired
The id of the application
requirementIdstringRequired
The id of the requirement slot
Request
This endpoint expects an object.
requirementVersionintegerRequired
Current version from the event or list. 409 if stale.
outcomeenumRequired
Allowed values:
reasonCodestringOptional
Required — an ESCALATION code on ROUTE_TO_COMPLIANCE, a REPLACEMENT code on REQUEST_REPLACEMENT; 400 without, or on category mismatch. Omit on APPROVE / REQUEST_CORRECTION.
explanationstringOptional
Required when the reason code has requiresExplanation.
recommendedActionstringOptional
documentIdstringOptionalformat: "uuid"
reviewCategoryenumOptional
confidencedoubleOptional0-1
criteriaobjectOptional
Echo of the slot’s criteria (criteriaId, version) as returned by the requirements list.
modelVersionstringOptional
promptVersionstringOptional
rulesAppliedlist of stringsOptional
evidenceRefslist of objectsOptional
extractedFieldsmap from strings to anyOptional
Response
The finding was recorded and the slot transitioned
findingIdstringOptionalformat: "uuid"
statusenumOptional
requirementVersionintegerOptional
Errors
400
Create Requirement Finding Request Bad Request Error
404
Create Requirement Finding Request Not Found Error
409
Create Requirement Finding Request Conflict Error
Available by Request
The core agent write. Post one finding per slot, evaluated against the slot’s criteria, reporting one outcome. The outcome is the slot transition: APPROVE → APPROVED_BY_CORA · REQUEST_REPLACEMENT → WAITING_ON_APPLICANT / REPLACEMENT_REQUESTED · REQUEST_CORRECTION → CORRECTION_IN_PROGRESS · ROUTE_TO_COMPLIANCE → NEEDS_COMPLIANCE_REVIEW.
Agents have no status PATCH: IN_REVIEW is set by Fortress when it dispatches requirement.upload_received; the finding is the only way out. Fortress publishes the matching requirement.* event (echo-suppressed for the agent that wrote it).
400 — missing or mismatched reasonCode, finding against a FORM slot. 409 — stale requirementVersion, slot already APPROVED_BY_COMPLIANCE, household paused.
This endpoint is part of the document-review agent surface. To explore availability for your integration, please contact our team.