What a GoodLeap Pros integration can actually reach

Type a homeowner's name and address into GoodLeap Pros and, within seconds, a soft-credit pull comes back carrying several priced loan offers. That round trip — applicant in, multiple decisioned offers out — is the surface most teams actually want, and it is the spine of this brief. GoodLeap, the lender behind the app, was Loanpal until a June 2021 rebrand (per its Wikipedia entry) and runs a point-of-sale platform for solar, roofing, HVAC, batteries and other sustainable home upgrades. The contractor holds the account; the homeowner consents at the point of sale; the data lives on GoodLeap's origination and servicing backend.

Data behind the contractor login

Each row below is a real surface of the app, named the way a rep would recognise it. Field names get pinned during the build; the shape here reflects what GoodLeap Pros surfaces in its own sales flow.

Getting to the data — the routes that apply here

Three routes are realistic for this app. We name the one we would run and why.

Authorized interface integration and protocol analysis

We map the app's authenticated traffic — the prequalify request, the decision response, the pipeline list, the payments calls — under the contractor's own consented account, then rebuild those flows as a clean, documented service. Reachable: the full offer-and-decision round trip plus pipeline and funding state. Effort: moderate; the offer object is consistently structured across the app's sales flow. Durability: good, with a maintenance step for GoodLeap app releases. This is the route we recommend as the backbone — it gives live offers and decisions without waiting on anything external.

User-consented operation of the contractor account

For teams that want the integration to act as their own reps do, we operate within the contractor's GoodLeap Pros session under an agreed scope, so prequalify, decision and pipeline reads run on schedule. Reachable: the same surfaces as above, driven on the contractor's behalf. We arrange the credential handling and scope with you during onboarding; it is part of the work, not something you sort out first.

Servicing-side export reconciliation

Once loans are funded, the servicing side carries statements and payment history. We use that as a batch backstop to reconcile funded volume and payouts, where near-real-time pipeline data is not required. It is slower and after-the-fact, so it complements rather than replaces the live route.

The prequalify call, sketched

This is the flow most integrations are built around. Field names are illustrative and confirmed during the build; the soft-pull boundary shown here is the part we treat as load-bearing.

# Authorized interface integration — GoodLeap Pros offer flow
# Session is established from the contractor's own consented login.

POST /pros/v*/applicants/prequalify
Authorization: Bearer <contractor_session_token>
{
  "contractor_account_id": "...",
  "applicant": {
    "first_name": "...", "last_name": "...",
    "property_address": { "line1": "...", "state": "TX", "zip": "..." },
    "stated_income": 0,
    "ownership": "owner",
    "consent_soft_pull": true
  },
  "project": { "type": "solar|roofing|hvac|battery", "gross_amount": 0 }
}

200 OK
{
  "decision": "approved | conditional | declined",
  "application_id": "...",
  "offers": [
    { "product": "loan", "apr": 6.99, "term_months": 300,
      "monthly_payment": 0, "flexpay_window_months": 18,
      "dealer_fee_tier": "...", "stipulations": [] },
    { "product": "ppa",  "...": "..." },
    { "product": "lease","...": "..." }
  ]
}

# 401 -> re-run the consented login handshake (token rotates)
# 409 -> applicant already in pipeline; fetch by application_id
# Note: prequalify is a SOFT pull. A hard pull fires only at contract.
      

What lands at the end of the build

Everything is scoped to the surfaces above, not a generic kit:

• An OpenAPI specification for the prequalify, decision, pipeline, milestone and payments calls as they behave for a real contractor account.
• A protocol and auth-flow report: how the contractor session token is obtained, how it rotates, and where the soft/hard credit boundary sits.
• Runnable source for the key endpoints in Python or Node.js, including the re-auth handshake and the de-duplication keyed by contractor, branch and rep.
• Automated tests covering the approved / conditional / declined paths and the 401/409 cases.
• Interface documentation a non-specialist on your side can follow, plus data-retention and consent-logging guidance fitted to the soft-pull step.

Consent and where GoodLeap sits in US data rules

GoodLeap is a nonbank originator and servicer of closed-end installment loans for home improvement, and the GoodLeap Pros account belongs to the contractor, not the homeowner. The homeowner's consent attaches to the soft-credit step at the point of sale, which makes that consent and its logging the part we treat most carefully — soft pulls are FCRA-relevant and we keep records of who consented to what and when. The CFPB personal financial data rights rule (12 CFR part 1033) centers on Regulation E asset accounts and Regulation Z credit cards; GoodLeap's installment loans sit outside that core, and the rule is itself in reconsideration following the CFPB's August 2025 advance notice, so it is not the access lever here and we do not build around it. The lever is the contractor's authorization over its own account plus documented homeowner consent. We pull only the pipeline, offer and decision fields the integration needs, work under NDA where the contractor asks, and keep an access log.

Things we account for in a GoodLeap Pros build

Concrete points specific to this app that we handle as part of the work:

• Offers are not one rate. Pricing changes by loan program, by state, and by the contractor's dealer-fee tier, and GoodLeap's FlexPay structure means an interest-only window (reported around 18 months in consumer-finance coverage of its terms) before re-amortization. We snapshot the full offer set per program and state rather than reducing it to a single APR, so a contractor on a different program still sees correct numbers.
• The soft/hard credit boundary is load-bearing. Prequalify is a soft pull; the hard pull only fires at contract. We design the sync to stop at the soft-decision boundary unless the contractor explicitly drives the contract step, so no integration ever triggers an unintended hard inquiry on a homeowner.
• One account, many reps. A contractor account spans branches and individual reps. We key records by account, branch and rep and de-duplicate homeowners who appear in more than one pipeline, and we keep a re-validation step in maintenance so a GoodLeap app release that shifts the request shape is caught before it breaks the sync.

Where teams point this integration

• Push every new GoodLeap Pros prospect, offer set and decision into the contractor's CRM in near real time, so management sees the funnel without logging into the app.
• Call the prequalify flow from the contractor's own proposal tool, so reps present GoodLeap offers without leaving the quote they are building.
• Match funding milestones and payouts against the contractor's accounting to close the loop between installed work and money received.
• Normalise GoodLeap offers alongside other lenders into one schema so a rep compares options on a single screen.

Sources and what we verified

Checked in May 2026 against the public app listings, GoodLeap's company record, a partner integration's published configuration, and the current US data-rights position. Primary references opened: GoodLeap Pros on the App Store, the GoodLeap company entry on Wikipedia, Aurora Solar's GoodLeap sales-mode integration help, and the CFPB's personal financial data rights reconsideration page.

Mapped by the OpenBanking Studio integration desk, May 2026.

Other lenders in the same sales motion

Same category, named so a unified integration can be scoped across them. Plain ecosystem context, no ranking.

• Mosaic — point-of-sale solar and home-improvement loans originated through contractors, with a comparable pipeline-and-offer flow.
• Sunlight Financial — a point-of-sale solar and home-improvement loan platform built around a contractor sales process.
• Dividend Finance (a Fifth Third Bank company) — residential solar and storage loans applied for through contractors.
• Sungage Financial — long-term residential solar loans with a contractor-facing portal.
• Regions Home Improvement Financing (formerly EnerBank USA) — contractor-driven home improvement installment loans.
• GreenSky — home improvement point-of-sale financing spanning many trades.
• Service Finance Company — HVAC, roofing and home improvement point-of-sale loans.
• LightStream (a Truist division) — unsecured solar and home improvement loans applied for directly.
• Sunnova — residential solar financing alongside a homeowner servicing and monitoring app.

Screens from the app

Store screenshots, for interface reference. Click to enlarge.

Questions integrators ask about GoodLeap Pros

Does pulling offers through an integration trigger a hard credit inquiry on the homeowner?

No. The prequalify path in GoodLeap Pros runs on a soft-credit pull; a hard pull only happens at the contract step. We design the sync to stop at the soft-decision boundary unless the contractor explicitly drives the contract, so an integration never sets off an unintended hard inquiry.

Can offers be split by GoodLeap program and state, or is it one blended rate?

Offers vary by loan program, by state, and by the contractor's dealer-fee tier. We map them per program and per state and preserve the FlexPay interest-only window rather than collapsing everything to a single APR.

We run several reps and branches under one GoodLeap Pros account — can the data be split per rep?

Yes. Records are keyed by contractor account, branch and rep, and homeowners who show up in more than one rep's pipeline are de-duplicated so dashboards stay clean.

Is GoodLeap covered by the CFPB personal financial data rights rule?

GoodLeap's closed-end installment loans sit outside the Regulation E and Regulation Z credit-card core that the CFPB 1033 rule centers on, and that rule is in reconsideration as of the August 2025 advance notice. The access basis we use is the contractor's authorization over its own account plus the documented homeowner consent for the soft-credit step.

Working with us on this

Source for the GoodLeap Pros prequalify, decision, pipeline and payments calls ships as runnable Python or Node.js from $300, invoiced only after it is delivered and working to your satisfaction; or skip the build and call our hosted endpoints instead, paying per call with nothing upfront. Either way the cycle is one to two weeks, and access and compliance are arranged with you as part of the engagement rather than asked of you in advance. Send the app name and what you need from its data through our contact page and we will scope it.