Available Tools
To facilitate rebate transactions, states will require a combination of IT systems and personnel to work with implementers and/or other service providers. PNNL and DOE developed the Application Programming Interface (API)—also known as the DOE Rebate Tracking System and Coupon Generator—to facilitate program implementation and reduce reporting requirements. When utilized in tandem with the PNNL Quality Install Tool, the DOE API streamlines the rebate issuing, redemption, and reporting procedures while the Quality Install Tool simplifies the process of collecting the required quality installation documentation.
Application Program Interface (API)
DOE and PNNL created an API that will provide a set of rules and protocols to allow external entities to connect to the national rebate tracker. In the context of the Home Energy Rebates programs, the Rebate API serves as a bridge between the central database, external systems, and the internal Address API that protects personally identifiable information (PII).
The purpose of the API is to facilitate the reporting of program data to DOE by enabling authorized stakeholders, such as state energy offices and implementers, to securely access and report the required information. By streamlining the data reporting process, the API enhances transparency, accuracy, and efficiency in tracking and analyzing the program's impact.
Development Overview
To implement the Home Energy Rebates program, the state, territory, or Tribe is responsible for pursuing one of the following implementation pathways to interact with the DOE/PNNL Rebate Tracking System:
- DOE Option 1: Build a connection to the DOE/PNNL API for a real-time connection.
- DOE Option 2: Build a connection to the DOE/PNNL API for monthly reporting purposes.
- DOE Option 3: Use the DOE-provided spreadsheet and upload it on the DOE/PNNL portal for manual monthly reporting purposes.
Development Updates
The current version of the DOE/PNNL API is intended to support and be consistent with the DOE Data and Tools Guide.
Changelog
Please see API Schema Documentation to stay up to date with API versioning.
Summary of changes to support API and be consistent with Program Notice 26-1 and 26-2.
| No. | Change | Program | API Users (Real-Time & Bulk) | Spreadsheet Users | Breaking Change |
| 1. | DAC removal for 50122 | 50122 | “is_disadvantaged_community” and “contractor_dac_incentive” data fields will be removed | “is_disadvantaged_community” and “contractor_dac_incentive” data fields will be removed | Yes |
| 2. | DAC map selection for 50121 | 50121 | States must notify PNNL whether they intend to use the Address Service API for disadvantaged community (DAC) status verification. States that plan to use the Address Service API to determine the DAC status of an address must provide PNNL with the DAC map they intend to use no later than August 1, 2026. States planning to use the currently loaded maps should also confirm this with PNNL. This requirement applies to all states that are actively using the API. States that do not intend to use the Address Service API for DAC status verification will be required to begin reporting the is_disadvantaged_community” data field in the reservation. | Possible | |
| 3. | Restrictions on non-electric to electric appliance upgrades | 50122 | Reservations for following upgrade types: Heat Pump Water Heater, Heat Pump Clothes Dryer and Electric Cooking Appliance will be rejected if “fuel_type” data field is a non-electric fuel | Reservations for following upgrade types: Heat Pump Water Heater, Heat Pump Clothes Dryer and Electric Cooking Appliance must not include non-electric fuel in the data field “fuel_type” | Yes |
| 4. | Heat Pump Changes | 50122 | Additional attestation field: For the product type “HEAT_PUMP_FOR_SPACE_HEATING_OR_COOLING” there will be an additional attestation for homes with non-electric HVAC systems installing a Heat Pump. This attestation affirms that the dwelling will retain existing fossil-fuel HVAC systems when installing a heat pump, even if the heat pump will not become the primary source of heating and cooling | Additional attestation field: For the product type “HEAT_PUMP_FOR_SPACE_HEATING_OR_COOLING” there will be an additional attestation for homes with non-electric HVAC systems installing a Heat Pump. This attestation affirms that the dwelling will retain existing fossil-fuel HVAC systems when installing a heat pump, even if the heat pump will not become the primary source of heating and cooling | Yes |
| 5. | New construction cost-effectiveness attestation | 50122 | Addition of a new attestation field for project type ‘new construction’ | Addition of a new attestation field for project type ‘new construction’ | Yes |
| 6. | Mail-in rebate disclosure | 50122 | Addition of an optional field to report a mail-in rebate “is_mail_in_rebate”: true | Addition of an optional field to indicate there was a mail-in rebate “is_mail_in_rebate”: true | No |
| 7. | Insulation and Air Sealing Prerequisite Attestation | 50122 | Addition of a new attestation to Limited Home Assessment “insulation_and_air_sealing_prerequisite_attestation” | Addition of a new attestation to Limited Home Assessment “insulation_and_air_sealing_prerequisite_attestation” | Yes |
| 8. | Expanded DIY eligibility | 50122 | Allowing all upgrade types except “HEAT_PUMP_FOR_SPACE_HEATING_OR_COOLING” to be a DIY reservation | Allowing all upgrade types except “HEAT_PUMP_FOR_SPACE_HEATING_OR_COOLING” to be a DIY reservation | No |
| 9. | Reservation Date | Both | Addition of optional field “project_reservation_date” | Addition of optional field “project_reservation_date” | No |
| 10. | Multifamily Building Identification Extension | Both | When applicable, include a new field “building_name_or_number” | When applicable, include a new field “building_name_or_number” | No |
| 11. | Safety Checks change | Both | Update on attestation language within existing safety checks field | Update on attestation language within existing safety checks field | No |
| Non–API changes | |||||
| 12. | Removal of Energy Star's requirement for 50121 post-retrofit files. | No changes in reporting to the API. For ‘50121 post-retrofit files “If HP added, does it meet Energy Star's requirement for cold climate HPs?” will no longer be required | No changes in reporting to the API. For ‘50121 post-retrofit files “If HP added, does it meet Energy Star's requirement for cold climate HPs?” will no longer be required | No | |
| 13. | Removal of requirement for “Geotagged photos of all home components that were upgraded” in 50121 | The photos were previously required to be retained and are no longer required to be retained. | The photos were previously required to be retained and are no longer required to be retained. | No | |
| 14. | Allowance to direct rebate payments to a third-party aggregator, such as a lender, in 50121. | No reporting changes. States must retain this information. | No reporting changes. States must retain this information. | No | |
Accessing the APIAt this time, anyone can access the API in sandbox test for testing purposes. You will need a username and password. To request testing credentials, email the development team at RebateTools@pnnl.gov.
Access the API in Sandbox-test Only authorized users may access the production API. All contacts provided in the pre-launch data details will have a production API account created automatically. Requests for production API accounts must come from the state’s, territory’s, or Tribe’s official point of contact. |
API Schema DocumentationThe IRA Rebates API GitHub repository is intended to contain materials useful to users of the IRA Rebates API. A folder has been added containing JSON Schema files that are used by the IRA Rebate API to validate the JSON payload of each POST endpoint. API users may find these files useful as documentation and as an aid to early development. |
Spreadsheet Reporting
DOE and PNNL recognize that full integration with the DOE API may not suit every need. With that in mind, a possible integration path is to use the DOE API for spreadsheet reporting, which allows for manual data entry and submission without full integration. There are two spreadsheets, 50121 and 50122 (links below are spreadsheets that correspond to Data and Tools Guide version 2), which can be used together or independently, allowing for a split-process approach where one rebate program can use spreadsheet reporting while another utilizes full integration. Programs have the flexibility to decide when to rely on existing infrastructure and when to integrate with the DOE API, ensuring the most efficient and effective reporting process for their needs.
Quality Install Tool
PNNL’s Quality Install Tool is open source and can be used to support the Home Energy Rebates programs. The Quality Install Tool simplifies, standardizes, and expedites the creation of high-quality installation documentation using geotagged, photo-based prompts throughout the process, and automatically generates a presentable Quality Install Report PDF that can be saved, emailed, or printed. Relevant Quality Install Tool workflows will continue to be updated in the web app.
Geotagging Resources
Capturing Geotagged Photos
Transferring Geotagged Photos
Viewing Geotagged Data in Photos