Skip to navigation
Questions

What facts does each line need?

Capabilities list the required facts of each line, with a JSON Schema of its application.
View as Markdown

GET /v1/capabilities answers with one entry for each line your key can quote. Add line to get one line:

curl "https://api.truvo.com/v1/capabilities?line=renters" \
  -H "Authorization: Bearer $TRUVO_API_KEY" \
  -H "Truvo-Version: 2026-09-26"

Each entry gives:

  • required_facts: the path of each fact that a request of the line must give, such as application.applicant.email.
  • required_facts_schema: a JSON Schema of the line’s application. It describes every fact the line takes, and its required list names the parts that a request must give.

Build the application from the schema, and ask the person for each fact it needs. Don’t fill in a fact with a guess.

Facts that depend on the request

Some facts are required only in some cases. For example, an auto request in Pennsylvania also needs application.protection.tort_type. When one is missing, the needs_information answer names it.

When a fact is missing

If a required fact is missing, Truvo doesn’t ask any carrier. POST /v1/quote-requests answers 422 with the code needs_information, and field_errors lists the path of each missing fact. Add the facts, then send the request again. See Errors.

Facts you leave out

When a request leaves out an optional fact, Truvo can use a default. Check both places where defaults appear:

  • The quote request’s assumptions lists the defaults that Truvo set before it asked carriers.
  • Each quote’s evidence.assumptions lists every default that the quote rests on. A quote can add its own, such as the start date of a renters quote when the request gives none.

Each default has a path, a value, and a source. To change a default, send the fact.

A carrier can still answer missing_information when it needs a fact that the request didn’t give. See Why did a request finish with no quotes?.