Subscribe to these events via Webhooks to track Task progress and data availability in real time.
All webhook payloads include these common fields:
| Field | Description |
|---|
webhook_id | Unique identifier for this webhook request |
event_type | The event classification |
event_created_at | Timestamp when the event occurred |
user_id | Associated Truv user identifier |
| Field | Description |
|---|
task_id | The Task identifier |
link_id | Account connection ID (use to retrieve access_token) |
product | The product the event relates to, such as income, employment, or assets |
data_source | Source of data: payroll, docs, insurance, financial_accounts, or tax |
tracking_info | Custom metadata passed via bridge_token (nullable) |
status | Current task status (see Connection Lifecycle) |
updated_at | Time event occurred |
template_id | Associated template, if applicable (nullable) |
task-status-updated
Fires for each Task status change during the connection lifecycle. This is the primary event for tracking verification progress.
{
"webhook_id": "488f424096d3461aa0e4cf11a985f6df",
"task_id": "521442a087604e599c637db310d07402",
"link_id": "d39d86dcc20c46e0ae75ba9ab1311a21",
"product": "income",
"data_source": "payroll",
"tracking_info": null,
"event_type": "task-status-updated",
"event_created_at": "2022-08-24T13:55:12.845645Z",
"updated_at": "2022-08-24T13:55:12.845666+00:00",
"status": "done",
"user_id": "88fef4cea64c40b5ad6727cc9b0b9fdc",
"template_id": null
}
When status is done, all data has been downloaded and processed. This is when you should fetch verification reports.
