Cancel Application

Defined, not yet published

CORA asks Fortress to cancel an application; Fortress performs the cancellation. This is CORA’s only application-level action. CORA calls it in two situations from the Nudging flow:

CADENCE_EXPIRED: the applicant has gone more than 7 days without interaction after the last touchpoint.
APPLICANT_REQUESTED: the applicant replied (message.received) and the intent of the reply is to cancel or end the process.

In both cases CORA sends the final message first (Send message, Fern), then calls this endpoint. After the cancellation Fortress sends application.completed with status CANCELED, like any final status, and CORA stops all work on the application and cancels pending touchpoints. Only a Fortress user can reverse a cancellation.

Fortress is still aligning with Fission Labs (CORA) how CORA handles a household where one adult never responds.

This route is defined for the CORA integration and is not delivered yet. Fortress does not serve it until it moves to Available. Authenticate with the x-api-key header.

Authentication

x-api-keystring

API Key authentication via header

Path parameters

applicationIdstringRequiredformat: "uuid"

The application.

Request

This endpoint expects an object.

reasonenumRequired

CADENCE_EXPIRED: more than 7 days without interaction after the last touchpoint. APPLICANT_REQUESTED: the applicant asked to cancel.

Allowed values:

Response

Application cancelled. A repeated call for an application already cancelled by CORA also returns 204.

Errors

400

Bad Request Error

401

Unauthorized Error

404

Not Found Error

409

Conflict Error