Skip to main content
Truv Bridge emits client-side events during the user’s connection flow. These are JavaScript callbacks configured when you initialize TruvBridge.init(). They are distinct from server-side webhook events.
  • Callbacks: Responses for specific Truv Bridge actions
  • Event data: onEvent types 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 on OPEN and DOC_UPLOAD_OPENED events.

ScreenViewData


EmployerSelectedData


DocumentsUploadedData


TaskData

Present on LINK_CREATED, LOGIN_COMPLETE, and SUCCESS events.

ErrorData


CloseData


ManualDDSData


OAuthEventData


Errors

Design your UX to surface login errors to borrowers in real time. When onEvent fires with type ERROR and error_code: LOGIN_ERROR, prompt the user to re-enter their credentials rather than silently failing.

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.
  1. Detect the error. Register an onEvent callback when initializing Truv Bridge. When onEvent fires with type ERROR, inspect the error_code in the payload.
  2. Close Bridge. After capturing the error details, close the Bridge widget programmatically or wait for the user to close it via onClose.
  3. 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.
Track which error_code values trigger manual fallbacks in your analytics. A high rate of UNAVAILABLE errors for a specific provider may indicate a temporary outage, while frequent LOGIN_ERROR events may point to a UX issue in your credential entry 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