TruvBridge.init(). They are distinct from server-side webhook events.
- Callbacks: Responses for specific Truv Bridge actions
- Event data:
onEventtypes and their payload shapes - Errors: Bridge error objects, types, and codes
Callbacks
The Embedded Orders flow uses a different callback signature. See Embedded Orders for the correct initialization pattern when using
isOrder: true.Event data
onEvent Types
CommonEventData
Present onOPEN and DOC_UPLOAD_OPENED events.
ScreenViewData
EmployerSelectedData
DocumentsUploadedData
TaskData
Present onLINK_CREATED, LOGIN_COMPLETE, and SUCCESS events.
ErrorData
CloseData
ManualDDSData
OAuthEventData
Errors
Error Object
Error Types
Error Codes
Route errors to manual fallback
When Bridge encounters an error, intercept it client-side and route the user to a manual verification workflow instead of dead-ending the experience.- Detect the error. Register an
onEventcallback when initializing Truv Bridge. WhenonEventfires with typeERROR, inspect theerror_codein the payload. - Close Bridge. After capturing the error details, close the Bridge widget programmatically or wait for the user to close it via
onClose. - Route to fallback. Based on the error type, redirect the user to your manual process — document upload, paper form submission, or a support contact flow.
Bridge errors are client-side events, distinct from server-side webhook events and task status changes. Use both in combination: Bridge
onEvent for real-time UX routing, and webhooks for backend workflow orchestration.Next steps
SDKs & Libraries
Install Truv Bridge for web and mobile
Task Events
Server-side event reference for task and data-object events
Connection Lifecycle
Task status flow referenced by Bridge events
Deeplinking
Skip employer search to improve conversion