Changelog

Get the latest feature updates in Truv

Loan application number: The loan object on an order now accepts an application_number (the POS file number) as an alternative to loan_number. A loan must supply at least one of the two identifiers; loan_number is no longer required on its own. The new field is returned in the loan object on order create, retrieve, and list responses, so if you validate responses against a strict schema, update it to allow application_number.

This supports POS-first workflows where the file exists before the LOS has assigned a loan number. If you currently send a placeholder in loan_number, we recommend moving that value to application_number and populating loan_number only once the real one is assigned. In the near future, loan_number will no longer be editable once set, and attempts to change it will be rejected. That change will be announced separately.

See the Loan object reference for the full loan schema.

Provider category field: We're adding a new category field to the Data Provider object that classifies each provider by the type of income it represents: w2 for traditional W-2 payroll employers, gig for gig-economy platforms, and benefits for government benefits providers.

The field will be returned by the List providers (GET /v1/providers/) and Retrieve provider (GET /v1/providers/{id}/) endpoints starting August 6, 2026. This is an additive change and requires no action for most integrations. If you validate API responses against a strict schema, update it to allow the new category field before then.

See the Data Provider object reference for the full schema.

List orders endpoint: You can now retrieve a paginated list of your orders with the new List orders endpoint (GET /v1/orders/).

The endpoint uses cursor-based pagination and supports filtering by date range, status, product, source, and more, plus full-text search across fields like order number, loan number, and applicant name. This lets you pull orders in bulk without knowing individual order IDs.

See the List orders API reference for the full request and response schema.

API Changelog items

  • Deprecation of is_closed in the Loan object: The is_closed field has been removed from the /v1/orders/ API documentation is being prepared for removal from the response. Users are advised to stop relying on this field to avoid disruptions. To indicate that a loan has closed, set the funding_date field on the Loan object via the Update an order endpoint instead. Affects the Loan object returned by:

TLS security enhancement: As part of our ongoing security program, we are updating the cipher suites used on Truv's public endpoints during our next major upgrade. Truv already requires TLS 1.2 or higher, and that minimum is not changing.

For nearly all integrations this change is transparent and requires no action. We do not expect any service interruption.

What is changing: We are removing one cipher suite, TLS_CHACHA20_POLY1305_SHA256. All other supported cipher suites remain available. A client is affected only if it relies on this cipher alone and cannot use a standard AES-GCM cipher suite. This is rare, since every mainstream HTTP client and runtime supports AES-GCM by default.

API Changelog items May 05

  • New income category values: INTEREST, INVESTMENT, OTHER: The income_category field on bank income sources now returns three additional values: INTEREST (interest on deposit accounts), INVESTMENT (dividends and brokerage distributions), and OTHER (unclassified deposits). Transactions previously returning a null income_category for these deposit types will now be categorized going forward. Historical records already retrieved may still show null. These are treated as non-recurring income.

    Available in:

  • Introduced new product names for Truv’s verification suite: Truv has introduced new product names for our suite of verifications that will display in Truv Dashboard, Truv templates, Truv Create order form, Truv orders, and integrated systems.
Truv Dashboard showing renamed verification products
Dashboard Improvements
  • Link is suspicious column in Orders and Users tables: To provide quick reference for suspicious links in Truv Dashboard, we have added a 'Suspicious' column to the Orders and Users tables, showing if the latest task for each provider is suspicious.
  • Latest error message in 'Connections' for Orders and Users: To make troubleshooting unsuccessful connections easier, we have added the Error Message for the latest attempt for each provider to the 'Connections' section in Orders and Users.
  • Performance per Template in Reporting: To improve visibility into verification volume and performance, we have added a table to show volume and conversion by template and initial vs. refresh order to the Dashboard Reporting tab.
  • Self-Employed Income report template customizations: For public sector customers who want to control which account or transaction categories are included in the Self-Employed Income report JSON and PDF, we have added the ability to filter categories in Truv templates. Additionally, templates also support customizing which categories are visually labeled in the report PDF.
  • Bulk upload orders enhancements for Public Sector: In Truv Dashboard, public sector teams can now upload a CSV file to bulk create up to 100 orders at a time, instead of one-by-one. We have enhanced this feature to support additional Truv products, including Self-Employed Income, Wage Earner Income + Self-Employed Income, and fields (status updates), as well as clarified instructions.

Added order retrieve endpoint to return additional financial account details: balance (the current account balance, when available), owners (list of account owners), and bank_income_sources (income sources derived from transaction data, when available). All new fields are read-only and nullable.

Available in:

  • New order-created webhook event: Customers can now subscribe to an order-created webhook event to receive a notification as soon as an order is created. See documentation for more details.
  • Optimized /v1/links/ API performance: Improved the underlying query for the /v1/links/ endpoint, reducing response times from ~5 seconds to ~1 second for customers with large link volumes.

Ready to get started?

Create an account today, or schedule some time with our team to learn more.