Device interval data must to be uploaded to the Leap platform for DSGS in California as well as Massachusetts Clean Peak Standard and ConnectedSolutions in New England in order to calculate baselines and performance, as well as generate revenue payments. We've now added SFTP server support to simplify the uploading of large files and enable automation via client libraries.

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.

You can now easily test your Connect API and Meters API integrations using the CAISO Staging Test Utility. This makes it easy to test various Connect scenarios as well as add meters in staging with different meter statuses.

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