Leap now offers additional ways to add meters to the Leap platform. In programs where customer utility account authorization is not required, partners can automate the enrollment of meters in grid services programs through these new endpoints.

Connect statuses on the Connect API and tab are now updated in real-time as customers click through the Leap Connect flow. Previously these statuses had been updated every hour but in order to enable quicker re-engagement of customers and improve conversion rates, this has now been changed to real-time updates. Check out the Customer Re-engagement developer guide for suggested re-engagement strategy and timing.

We recently updated some of our security protocols. As a result, the login token session duration has been reduced from 60 minutes to 30 minutes. This means that if you are using the login token to authenticate your requests to the Leap API endpoints, the token will expire after 30 minutes at which point you'll need to request a new token.

Leap’s new analytics capabilities, which have been available for partners to use for several months in beta, will become generally available (GA) shortly.

We’ve added example dispatches for each program across the various markets in order to simplify dispatch integration testing. As outlined in the updated dispatch Test Cases guide, you can select the relevant program from the request EXAMPLES drop-down menu in the webhook trigger test notification endpoints (meter | group) in order to pre-configure all of the request body parameters for that program. From there, simply change the appropriate parameters (e.g. meter_id, start_time, & end_time) for each test case.

The updated Leap Dispatch API (v2) is now available. As announced in April, this updated API makes it easier for Leap partners to prioritize multiple same-day or overlapping dispatches. It also helps partners to increase revenue by providing additional data points that help optimize dispatch strategies and performance. The updated Dispatch API (v2) supports automated notifications across the entire Leap value stack, providing real-time dispatching for all programs enabled through the Leap platform.

We recently posted some additional resources to make dispatch integration easier. Check out the Recipes tab or the 2 new dispatch recipes below for guidance on how best to process incoming notifications.

Why Migrate to Dispatch API version 2

As outlined below, we've transitioned from the .ac to .energy domain and changed the staging sub-domain structure. The new domains have been live since January and all documentation has been updated to reflect this change. While the old domains are still active and no deprecation date has been set, it is recommended to update your integrations to the new FQDNs as soon as you are able to.

• Expanded API support for Leap Connect. Partners can now track the status of meter connections through the API and improve conversions by automating follow-up for customers who have started but not completed the Leap Connect and utility authorization process. View the Connect overview developer guide for more details.
• Enhanced meter metadata. Updates to the meter metadata available through the API make it easier to sync meters and track changes. This includes a last-modified request parameter, as well as program name, enrollment periods and more added to each meter response. We’ve also made it easier to identify when a meter requires a partner action to be taken. Read the meter management developer guide for additional information.
• Additional authentication options. In addition to login-based temporary authentication tokens, partners can now create and manage their own API keys, making it easier to authenticate to Leap API endpoints.