Application Events
The following webhook events are triggered during the application lifecycle:
Application Events
| Event | Description |
|---|---|
| application.created | Triggered when a new application is created. |
| application.approved | Triggered when an application is approved. A Customer resource is created at this point. |
| application.denied | Triggered when an application is denied. |
| application.awaitingDocuments | Triggered when an application requires additional documents to proceed. |
| application.pendingReview | Triggered when an application is pending manual review by Unit. |
| application.canceled | Triggered when an application is canceled. |
Related Events
| Event | Description |
|---|---|
| customer.created | Triggered when a Customer resource is created after an application is approved. |
| document.approved | Triggered when an application document is approved. |
| document.rejected | Triggered when an application document is rejected. |
Listening for Events
To receive these events, you need to set up a webhook endpoint. See the Webhooks documentation for more information on configuring webhooks.
Example Event Payload
When an application is approved, you will receive an event similar to:
{
"data": [
{
"id": "1234",
"type": "application.approved",
"attributes": {
"createdAt": "2023-01-15T10:30:00.000Z"
},
"relationships": {
"application": {
"data": {
"type": "individualApplication",
"id": "10001"
}
},
"customer": {
"data": {
"type": "individualCustomer",
"id": "20001"
}
}
}
}
]
}
Event Flow
- application.created - Initial application submission
- application.awaitingDocuments (if needed) - Documents required
- document.approved / document.rejected - Document processing
- application.pendingReview (if needed) - Manual review required
- application.approved or application.denied - Final decision
- customer.created - Customer resource created (on approval)