AI Team MembersCORA

CORA integration — events

What Fortress sends, and when

Delivery, signing and retry follow the platform webhook contract. Every payload nests its fields under data. Events caused by CORA’s own API writes are not delivered back to CORA; staff actions on the same slot are.

One page per event under Webhook Events: payload, data fields, when it fires, when it does not. Envelope on every delivery: eventId, eventType, occurredAt, data. Headers: X-Fortress-Signature, X-Fortress-Event-Id, X-Fortress-Event-Type, X-Fortress-Delivery-Attempt.

Which events to subscribe to

  • Required: compliance_review.closed, agent.property_state_changed, agent.global_state_changed — without them CORA never learns when to resume.
  • Trigger work: application.activated, requirement.upload_received.
  • Invalidate work: requirement.upload_removed, requirement.changed, requirement.canceled, application.updated, compliance_review.opened.
  • Observe staff decisions: requirement.satisfied, requirement.replacement_requested, requirement.reviewer_finding_submitted.
  • End of involvement: application.approved.