Journeys Events

Use webhooks to get real-time updates on your Journey Applications

Alloy uses webhooks to notify you every time a significant event occurs during your Journey Application. Configure your listener to receive these status updates and automatically trigger reactions.

Journey Events

Events	Description
`started_application`	A new Application has entered our system
`started_evaluation`	The evaluation has begun and is in process
`data_request_evaluation`	More information about an applicant is needed for our system to advance
`reached_auto_decision_node`	This only applies to the batch endpoint. If user has uploaded the batch file specifying that the “auto-decision” feature should be used on a specific node, this webhook event is thrown when that node is reached
`completed_review`	An agent has completed a manual review of an Application. This may immediately cause the Application to complete, or may kick off another evaluation (or otherwise continue the Application)
`has_finished_sending_additional_entities`	For streaming applications, this event signals that the stream has closed on a Group Application, and no further entities may be submitted
`pending_review`	An evaluation is in the manual review state and needs to be reviewed to a final outcome
`pending_action`	For an external service or user action, the Application is waiting for either an external service response or for an outcome of a user action
`pending_action_expired`	an action node which has an expiration set on it has reached that time limit
`pending_documents`	The Application is waiting for additional documents to be uploaded
`pending_workflow_service`	A node containing an “async” service has been hit, and Alloy is still awaiting the webhook from that service
`pending_step_up`	A docV node has been hit, or any node that requires SDK Configuration. Alloy is awaiting documents to continue
`completed_evaluation`	The evaluation has been concluded
`completed_branch`	An applicant has completed their Journey
`completed_review_journey_application`	This event occurs when the Journey Application as a whole has been reviewed by someone (as opposed to `completed_review`, which happens when an individual entity gets reviewed)
`started_reconciliation`	Reconciliation Logic (including the Reconciliation Step if client is using it) has started but has not yet finished
`completed_reconciliation`	All applicants have completed their Journeys and an outcome has been reached based on the Journey's reconciliation logic
`completed_application`	All applicants have completed their Journeys and the Application is no longer open, regardless of whether an outcome was reached. This event will always fire for every Application, if there’s an outcome on this event, that will be the Application’s final outcome/decision
`application_expired`	The Journey has an expiration timeframe set on it, and at least one entity Application in the Journey Application has still not reached a terminal outcome by the time the expiration time is reached
`started_rerun_application`	A re-run has been created off of this Application.
`error`	An evaluation was unable to reach an outcome, either because of misconfiguration or because a downstream vendor did not return data we needed to continue