Applications

• Quote: a priced, indicative offer. A frozen snapshot of what we offered, when, and under which rules. Its options, inputs and eligibility never change; a changed input means a new quote. What people do with it, such as your client’s interest, is recorded on it afterwards.
• Application: a deal in progress toward a signed PFA and loan. It appears in your broker’s portal pipeline. Documents, requirements, the agreement and the loan accrue on it.

​

Status

processing → requires_information → ready_for_agreement → awaiting_signature → pending_activation → active

• Use status for the badge and requirements for the detail. During processing, blocking already lists what we know is missing. From awaiting_signature on, blocking is empty.
• If the borrower declines before anyone has signed, the application goes back to ready_for_agreement (or requires_information), and your broker can send a new agreement. If a signature was already on it, the application stays requires_information with AGREEMENT_DECLINED, and Bridgeline follows up.
• active and canceled are final. An active application can still owe items in requirements.outstanding, such as a policy number after signing.
• New statuses may be added. Treat one you don’t recognize as “in progress”.

​

Requirements

"requirements": {
  "blocking": [
    {
      "code": "MISSING_POLICY_NUMBER",
      "param": "policies[pol_2o9fj1oLkchQ9qNzyigGf8].policy_number",
      "description": "This policy has no usable policy number. ...",
      "due_by": null
    }
  ],
  "outstanding": []
}

• blocking holds the finance agreement back, except the shown-early codes, which are listed for visibility. When nothing else is in it and the agreement hasn’t gone out, the status is ready_for_agreement.
• outstanding is owed after signing, by due_by, and never holds up the agreement. For a missing policy number or document, due_by is 30 days after the agreement is executed (the deadline for the carrier notice), and null until then. CARRIER_UNMATCHED and INSURED_ADDRESS_INCOMPLETE have no deadline of their own, so their due_by is null.
• param says where the fix goes: a policy field (policies[pol_…].policy_number), insured.address, signer.borrower or pricing, or null when no single field applies.
• Branch on code. Codes are never renamed, and new ones may be added: show description for a code you don’t recognize.

​

Missing policy numbers

​

Shown early

​

Pricing and the quote

• pricing is the terms your broker has priced in the portal: the ones the finance agreement will carry, and once it’s sent, the agreement’s own terms. It’s null until the application reaches pricing. total_of_payments is the amount financed plus the finance charge, exactly as on the agreement. selected_by is broker when your broker picked the terms, system when they kept our recommendation.
• created_via says where the deal came from: api, portal or email.
• quote_id, accepted_option_id, client_reference_id and metadata are set when a deal starts from a quote you accept through the API. Accepting isn’t available yet, so today every application was started in the portal or by email, and these are null (and metadata is {}). To match a deal to a record in your system for now, use the insured’s name and the policies’ policy_number.

​

Following changes

1. Every few minutes, page through GET /v1/applications with limit=100. 500 deals is 5 requests, well under the rate limit.
2. Compare each application’s status and requirements with your copy, and update what changed.
3. Keep following active applications: their outstanding items can still clear or change.