Collect Data Authorizations
Help your end customers authorize their sites for participation in a grid services program.
Authorizations are instances of end users providing consent to participate in a grid services program, and share the requisite meter data.
Designing an effective authorization flow is critical to scaling a grid services program. Without an authorization, a customer cannot enroll or participate in a program.
To collect authorizations without any front-end development, Leap provides a Registration Link (URL). Embed this link into an email, web/mobile application, or any interface visited by your customers.
Working with a small set of customers? Paper/PDF authorization forms are also available.
2. Get your Registration Link
|Leap-generated name for your organization|
|string identifying the utility providing data access|
|(Optional) string available to link authorized customers to your internal system|
|CAISO||Pacific Gas & Electric (PG&E)||pge|
|CAISO||Southern California Edison (SCE)||sce|
|CAISO||San Diego Gas & Electric (SDG&E)||sdge|
Utilities not listed in this table are not currently supported for automated authorizations by the Leap Platform.
You can utilize an internal Reference ID to link Leap's records to your internal records. Every meter record that is created on Leap's platform will contain the reference ID as provided in the registration link.
3. Embed the link and Share
Embed the registration link in a customer-facing interface. Email campaigns and in-app notifications are commonly used to engage end customers.
Before sending, be sure that:
org-nameis specified correctly in the URL.
utility-idmatches the service territory of each end customer.
- You've setup a
refIdfrom your system to populate as a query parameter in the URL for each customer.
4. End-user authorization journey
Once the end-user navigates to the registration link that you provided by email, through an app or other means they can expect the following process:
- The end-user navigates to the Leap authorization flow through the registration link
- Leap redirects the end-user to the authorization flow from the specified utility
- Upon completion, the utility redirects the end-user back to Leap indicating a success
- Leap processes the successful authorization and redirects the end-user to the (partner specified) thank-you page
Thank you page
An URL can be configured to redirect the end-user to after completing the authorization flow The Leap Platorm provides two parameters to this page:
authorizationId an identifier to Leap's internal authorization record
referenceId the refId as specified in the authorization link you've provided to the user
authorizationId is currently informational only as it is the only record that can be shared at the time the authorization is completed. This could be used for troubleshooting but has not been needed for this purpose so far so this can easily be disregarded.
You can utilize the
referenceId to match the returning authorization to your internal records. However, as this is a simple HTTP GET request, anyone could be making such request back to your service. You should always ensure authentication and authorization of the user on your own platform.
If a thank you page has not been setup for you the Leap default is used:
You can setup a thank you page through our Partner Success team: email@example.com
5. Sync Inventory with the Meter API
As customers complete their authorizations, new Meters become available in the Search API. Set up a process to sync meter inventory to track conversion rates, collect metadata, and plan program enrollment.
Note: The reference ID provided with the authorization will be returned with the corresponding meter records that have been authorized through the registration link.