Overview
Understanding Journey Applications
What is a Journey Application?
A Journey Application is the record Alloy creates when you submit data about one or more entities - a person, a business, or both - to be evaluated by a Journey.
It is the central object in Alloy's onboarding flow: every API call, webhook, and decision is tied back to a Journey Application.
Core concepts
- Journey - A configurable decisioning flow you build in Alloy's dashboard. You may have multiple Journeys for different use cases.
- Journeys may include identity verification, fraud checks, KYB checks, document collection, and manual reviews. This could all be in one Journey or split across separate Journeys depending on your use case.
- Journey Token - The unique identifier for a Journey. Passed as a URL path parameter to specify which Journey processes an application.
- Entity - A person or business represented in the application. A Journey Application may include multiple entities.
- Status - Where the application sits in its lifecycle.
- Complete outcome - The final decision that an application reaches at completion.
For additional terms (Entity Application, Step-Up, Action Node, etc.), see Reference: Journey Application glossary .
How it works
When you submit data to the Create Journey Application endpoint, Alloy creates a Journey Application and routes it through the Journey you specify in the URL path.
Because Journeys can include asynchronous steps, like manual reviews (performed in Alloy's dashboard) or step-up verification (where the applicant uploads documents), a Journey Application has a lifecycle that may take seconds, minutes, or days to resolve. Alloy emits webhook events for every status change so your integration can react without polling.
When all decisioning is complete, the Journey Application reaches a terminal status (typically completed) and Alloy assigns an outcome (such as Approved or Denied).
How it fits in Alloy
Journey Applications sit at the center of Alloy's onboarding product. They are created by your integration, processed by Journeys you configure in the dashboard, and emit webhooks that drive your downstream account-opening flow.
Most other concepts in the Journeys API, such as entities, step-up, action nodes, and manual reviews, exist within the Journey Application lifecycle.