generated: '2026-07-19' method: searched source: https://developer.leap.energy/docs/leap-connect, https://developer.leap.energy/docs/collect-data-authorization, https://developer.leap.energy/docs/customer-reengagement, https://developer.leap.energy/docs/test-utilities summary: Leap ships no JavaScript element library, web components or embeddable widget SDK. Its one client-side surface is Leap Connect — a hosted, partner-branded web flow that the partner links or redirects customers into, rather than embeds. Everything else is server-side REST plus the Leap Partner Portal. components: - family: Leap Connect name: Leap Connect hosted authorization flow kind: hosted-redirect-flow docs: https://developer.leap.energy/docs/leap-connect description: Partner-branded, multi-market hosted flow that walks an end customer through connecting their utility account, supplying required program information, and e-signing any agreements the market or customer type requires. Where applicable Leap redirects the customer to their utility's login screen to authorize data sharing, then back into Connect, and finally to a partner-supplied Final Redirect URL. host: addleap.com (staging.addleap.com in staging) url_shape: https://addleap.com///getting-started?refId= configuration: Generated by the partner from the Partner Portal Connections tab via the "+ Connect link" button. Branding, e-sign forms and participating utilities are configured per partner. parameters: - name: refId required: false description: Partner's own identifier for the customer or site, carried through the flow so Connect sessions can be reconciled with partner systems. - name: Final Redirect URL required: false description: Where Leap returns the customer once the flow completes. embedding: Not an embeddable component — the documented pattern is to link to the URL from a point-of-sale flow, a mobile app install step, or a re-engagement marketing campaign. regions_documented: - California (CAISO) - New York (NYISO) - PJM - Texas (ERCOT) - PSE / SRP / TVA utility programs (letter-of-authorization only, commercial customers) events: Connect flow progress is reported back over the webhook events connect_session.updated and connect_session.authorization_updated, and read over the getConnections endpoint. testing: Staging demo utilities for CAISO and NYISO exercise the full flow — see sandbox/leap-sandbox.yml. loader_libraries: [] element_libraries: [] embedded_dashboards: published: false note: The Leap Partner Portal (partner.leap.energy) is a first-party application, not an embeddable or white-labelled dashboard product.