CORA API index

Every route below lives in the main API Reference. This page is the CORA-shaped index: what to call, when, and where it is documented. All calls use the organization-scoped API key in the x-api-key header. requirementVersion is required on every requirement write. Configuration and cadence are read-only for agents.

Before acting on any event

Route	Purpose
`GET /properties/{propertyId}/coraConfiguration`	Is CORA enabled for the property? Same contract as the Leslie configuration
`GET /households/{householdId}/coraConfiguration`	Is CORA enabled for the household? Act on `effectiveEnabled`
`GET /households/{householdId}/complianceReview`	Is a Manual Compliance Review open? While `OPEN`, every write returns 409

Starting work on an application

Route	Purpose
`GET /applications/{applicationId}`	The application record and its `status`
`GET /households/{householdId}` · `GET /customers` filtered by household	Household members and their applications
`GET /applications/{applicationId}/requirements`	The requirement slots: status, `waitingReason`, `uploadState`, `requirementVersion`, `criteria`, `lastFinding`
`GET /properties/{propertyId}/agents/cora/cadencePolicy`	The outreach cadence to execute for the household

Reference data — cache it

Route	Purpose
`GET /agentReviewReasonCodes` · `/{code}`	`ESCALATION`, `REPLACEMENT` and `OVERRIDE` codes; refresh on a new `taxonomyVersion`
`GET /documentReviewCriteria` · `/{criteriaId}`	The rules a slot’s document is evaluated against; cache by (`criteriaId`, `version`)

Reviewing a document

Route	Purpose
`GET /documents/{documentId}/downloadUrl`	Short-lived signed URL for the uploaded file
`POST /applications/{applicationId}/requirements/{requirementId}/findings`	The one agent write. `outcome` is the slot transition
`POST /applications/{applicationId}/corrections`	After `REQUEST_CORRECTION`: apply permitted changes to application answers
`POST /applications/{applicationId}/resignatureRequests`	After a correction touches a field that must be re-signed
`POST /applications/{applicationId}/requirements/{requirementId}/cancel`	Cancel a slot — whether agents may is still open

Operating the agent

Route	Purpose
`POST /properties/{propertyId}/agents/cora/alerts` · `GET`	Raise safety and operational alerts, e.g. `STUCK_OR_FAILED_WORKFLOW`

Not on the partner surface

Slot status transitions, enabling or disabling the agent, editing configuration or cadence, creating slots, re-running requirement rules, logging communications and opening site tasks are all Fortress-side. Events Fortress sends in return are listed on Events.