Get aggregated incentive calculations from multiple utility programs based on customer address and device
lookup: First-time customers or when you need fresh utility data (requires full address and device_ids or device_names)refresh: Returning customers using cached utilities (fastest, only requires reference_id)override: Replace all customer devices with new ones, then refresh calculationdevice_ids) or by your own equipment/product names (device_names). When using device_names, the API resolves them via your organization’s equipment map. See the Incentives API Guide for details on resolution behavior and handling partial matches.
The response distinguishes between programs the customer is eligible for (incentives.by_program) and the subset Leap can complete an application for today (processing_summary). When surfacing an offer to a customer, prefer processing_summary.incentive_amount over incentives.total_incentive_amount — see Processing Status for the full rationale. The connect_url is populated only when at least one processing-enabled program is eligible.
For detailed operation type behavior, device handling, and best practices, see the Incentives API Guide.API key for authentication. Include your Leap API key in the x-api-key header: x-api-key: leap_live_...
Customer address, building type, and device information for incentive calculation
Operation type: 'lookup' for new calculations with geocoding, 'refresh' for using cached utility data (faster), 'override' for replacing all customer devices
lookup, refresh, override "lookup"
Your internal reference ID for tracking this customer within your organization (unique per organization)
"external-ref-123"
Customer's address information. Required for 'lookup' operation, optional for 'refresh' and 'override' operations (uses stored address if not provided)
Type of building for which to calculate incentives. Required for 'lookup' and 'override' operations, optional for 'refresh' (uses stored building_type_id if not provided)
RESIDENTIAL, MULTIFAMILY, MANUFACTURED_HOME, COMMERCIAL "RESIDENTIAL"
Array of Leap device IDs to check incentives for. Required for 'lookup' and 'override' operations unless device_names is provided. Optional for 'refresh' (uses existing devices if not provided). Can contain duplicates. Cannot be combined with device_names.
[32, 44, 44, 44]Array of your equipment/product names to check incentives for. The API resolves these to Leap device IDs using your organization's equipment map. Required for 'lookup' and 'override' operations unless device_ids is provided. Not supported for 'refresh' operations. Cannot be combined with device_ids.
[
"Mitsubishi Hyper-Heat MSZ-RXT09",
"Rheem ProTerraDERA2060"
]Whether to create/update application records and return a connect_url
true
Optional custom fields to include in the webhook payload when your organization has a webhook URL configured (e.g. Project ID, Record ID). Only keys allowed by your org's webhook field_names config are merged into the POST body.
{
"Project ID": "proj-123",
"Record ID": "row-5"
}Supplementary customer fields applied at customer creation time. Only honored on lookup operations that create a new customer — ignored for existing customers and for refresh/override. Use the Applications PATCH endpoint to update an existing customer's fields.
{
"first_name": "Jane",
"last_name": "Doe",
"email": "jane@example.com",
"phone": "415-555-0100"
}Supplementary device fields applied at device creation time, indexed positionally to device_ids. Only honored on lookup operations that create new customer devices — ignored for existing customers and for refresh/override. Each entry is partial; common fields include purchase_price, purchase_date, installation_date, contractor_name. Use the Applications PATCH endpoint to update existing device fields.
[
{
"purchase_price": 1500,
"installation_date": "2026-03-01"
},
{ "purchase_price": 2000 }
]Successful response with aggregated incentive data
Information about the utility serving the address
Formatted address string built from the request address fields
"123 Main St, Apt 4B, San Francisco, CA, 94102"
All utilities whose service territory contains this address. The primary utility is selected from this list; the others are returned so partners can see when an address falls in an overlap region.
The building type that was used for the calculation
RESIDENTIAL, MULTIFAMILY, MANUFACTURED_HOME, COMMERCIAL "RESIDENTIAL"
Leap's internal customer ID (created or found based on reference_id and address)
453
Your internal reference ID that was provided in the request, echoed back for correlation
"external-ref-123"
Branded Connect URL where the customer completes their application. Populated only when create_application=true AND incentives.total_incentive_amount > 0; otherwise returned as an empty string.
"https://connect.incentives.leap.energy/your-company/refId/external-ref-123"
Number of programs that were evaluated for this address + building type combination
2
Subset of incentives covering only programs that Leap is currently set up to process applications for (i.e. by_program[].processing_enabled === true). Use this to decide whether to surface the Connect URL and a concrete offer amount to the customer — programs that aren't processing-enabled may still be listed in by_program but Leap cannot complete the application for them today.
Present when device_names was used and some names could not be resolved. The API proceeds with the resolved devices and reports unresolved names here.