Leap's new webhook platform is now available in beta! The initial meter.created event is currently supported with more events coming soon.

New meter configuration use cases are now available with the release of the Nominations API. Leap generally sets meter nominations on behalf of partners but occasionally partners need to suggest their own nomination values. Check out the developer guide to learn more!

Adding, removing, and viewing meters tags is now supported via API! One or more partner-defined tags can be placed on meters in order to help with the following scenarios.

The new version (V2) of Leap’s Meters API is now available. This new API offers improvements for partners working in multiple programs and markets and provides additional meter metadata and enrollment information not currently available in the V1 Meters API.

The Revenue API provides a set of endpoints for partners to access revenue data that has been earned by participating in grid services programs with Leap. Accessing preliminary and final revenue data in a timely manner helps increase efficiency as well as more quickly identify opportunities to improve revenue.

Leap is developing a new communication test tool to give partners a way to test their dispatch operations. This capability adds a new field to dispatch API event notifications which is considered a non-breaking change for existing integrations.

Leap provides access to programs that dispatch and measure performance at either the utility meter (e.g. residential home or commercial site) or the individual device (e.g. battery, EV charger, or thermostat). The “Leap meter” refers to the asset where dispatching and performance measurement occurs and where revenue is generated from. The Leap meter_id is the unique ID that is used to identify this asset.

The Create Meters use cases and endpoints are now out of beta and generally available. Coming next for these use cases will be support for creating ERCOT ERS meters.

meter_type and meter tags were added to the Get Meter and Search Meters API endpoint responses. Meter type indicates whether a Leap meter is referencing a utility meter (and all partner controllable devices behind it) or a single device (applicable for device-level programs). Meter tags are optional and can be used to group meters or indicate customizable meter attributes.

Historically, if a timeout or HTTP error was received on the push notification, the Leap dispatch webhook service would retry every 10 minutes for up to 50 minutes (5 max retries). To better support real-time programs and provide notifications as quickly as possible, retries now happen every 1 minute for up to 50 minutes (50 max retries).