/api/v1/pricing/finance endpoint surfaces finance pricing context from the same finance_fees dataset that backs /api/v1/finance/fees, but returns data in a coverage-oriented shape designed for comparison and market research rather than direct quote calculation. The response wraps records in a coverage envelope that summarises filters, result counts, and the data source so callers can build dynamic lender-selection UIs, pricing dashboards, or CRM enrichment pipelines.
Endpoint
Finance Pricing vs. Finance Fees
Both endpoints draw from the samefinance_fees dataset and both require production access to it. The difference is in intent and response shape:
/pricing/finance | /finance/fees | |
|---|---|---|
| Primary use case | Market comparison, CRM display, pre-quote research | Quote calculation, proposal builders |
| Response shape | { records, coverage } with filter summary | Flat data array |
| Default limit | 100 (max 500) | 1000 (max 5000) |
| Additional params | limit configurable up to 500 | Same filters, higher cap |
quote_safe | Always true (same source) | Always true |
Request
Headers
Query Parameters
Filter by trade category. Accepted values:
solar, hvac, roofing, plumbing, electrical. Matched against trade_category (case-insensitive).Filter by payment product type (case-insensitive). Common values:
loan, lease, ppa, cash. Matched against the payment_type field.Filter by financier slug (e.g.
goodleap). Matched against the financier_slug field.Exact term filter in months. Must be a finite number or the request returns a
400 error.Exact interest rate filter as a decimal. Must be a finite number or the request returns a
400 error.Maximum number of records to return. Defaults to
100; hard cap is 500.Response
A successful response returnsdata.records (the pricing rows), data.coverage (a filter summary), and a usage block.
Response Fields
Array of finance pricing records. Each record is a quote-safe dealer-fee row from the
finance_fees dataset. See /api/v1/finance/fees for the full field-level reference — every field in that response is present here.Summary of the filters applied and result metadata.
Request metering information.
Examples
Example Response
Error Reference
| Status | Cause |
|---|---|
400 | term_months or interest_rate is not a finite number. |
401 | Missing or invalid x-api-key header. |
403 | Your key does not have production access to the finance_fees dataset. |
500 | Internal server error — contact support if this persists. |