Skip to main content
An Order is the starting point for every verification. When you create an Order, Truv automatically creates a User, generates a Bridge Token, and produces a personalized landing page for the user to connect their account. The following diagram illustrates the Order lifecycle.
Orders handle everything to get started: creating an Order is all you need to initiate a verification. The Order creates the User, generates the Bridge Token, and tracks the entire lifecycle from creation to completion.

What happens when you create an Order

  1. User is created automatically from the provided applicant details
  2. Bridge Token is generated for the Order
  3. Landing page is created with a unique share_url for the user
  4. Invite is sent (optional) via email, SMS, or both, or you can share the share_url directly
  5. User connects through Truv Bridge on the landing page
  6. Data is retrieved and the Order status updates as Tasks complete

Order lifecycle and webhooks

Orders are asynchronous. The typical flow is:
  1. You create an Order via the API or Dashboard.
  2. The user authenticates with one or more employers through Truv Bridge.
  3. Truv retrieves the data and fires a task-status-updated webhook for each employer/account as it completes.
  4. Truv fires an order-status-updated webhook each time a suborder — an employer or financial account — changes status, for example as each connection resolves.
  5. You retrieve the verification data from the Retrieve an order endpoint.
  6. Truv fires an order-finalized webhook once the order reaches its terminal state — no further data collection or refresh occurs.
In a multi-employer order, task-status-updated fires for every connection attempt, including failed logins. order-status-updated fires whenever a suborder — an employer or financial account — changes status, but not on individual login attempts. Use task-status-updated for fine-grained, real-time progress; use order-status-updated to track suborder status changes.
The no_data status means the user successfully connected to the provider, but the provider returned zero records. This is distinct from an error status, which indicates a connection failure. A no_data result typically means the provider has no history for the applicant, not that the connection failed.

Create orders

Create Orders through the Truv Dashboard or programmatically via the Create an Order endpoint. Orders are customizable for these components:
  • Landing page
  • Text message (optional)
  • Email (optional)

Attributes

The attributes of Orders are below.
Report limits: A single VOIE order supports a maximum of 5 employers, and a single VOA order supports a maximum of 5 financial institutions. If you need to verify more, create additional orders for the same user.
To get a PDF version of the report please use the corresponding report_id along with the GET endpoint in the User Reports section.
voie_report_id auto-population: The voie_report_id field is only populated automatically when an account-level setting is enabled. This setting generates a Fannie Mae DU / Freddie Mac LPA compatible report ID upon order completion. Contact Truv support to enable this feature for your account.

Company address object

The values in this table are for the address object of the company.

Employers object

View information for employer object field data below.

Provider object

This table contains data for the provider object.

Employments object

The Employments object contains the values and descriptions below.

Statements object

View the table below for information from the Statements object.

Annual income summary object

Find information for the attributes and values of the annual income summary object.

Bank accounts object

The table below covers the attributes within the bank accounts object.

W2s object

The values in this table are for the W-2s object field.

Company object

This table covers values within the company object.

Address object

The values in this table are for the address object of the company.

Insurance object

This table’s values contain information for the insurance object.

Financial accounts object

The financial accounts object attributes below have type information and descriptions.

Accounts object

Manager object

The manager object attributes below have information on type and description.

Loan object

View the table below for type and description of the attributes in the loan object.

Endpoints

The list below are the available endpoints for Orders.

Example response

The JSON object below is a sample response.