Reference · built on requestConnectorEnergy, EV & distributed resources

Leap API

Meter enrollment, program dispatch events, interval telemetry, and revenue settlement across wholesale grid services markets.

Request accessPricing ↗

About

Leap operates a distributed energy exchange connecting meters, batteries, electric vehicle chargers, and commercial loads to wholesale electricity markets. Its REST API allows partners to enroll meters in demand response programs across grid operators, receive dispatch event signals, stream interval telemetry, submit nominations, and track settlement performance.

Through Fibric, an operator monitors incoming dispatch notices and meter performance, proposing capacity nominations and dispatch response actions for human approval.

This is a reference listing. It documents what Fibric would read from Leap API and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Meter enrollment records and market participation status across regional transmission organizations
  • Active and scheduled dispatch events through the Leap Resource Dispatch and Program Dispatch endpoints
  • Interval meter telemetry and upload status through the Interval Data Upload API
  • Market bids, nominations, and registration refreshes across regional utility territories
  • Settlement calculations, baseline performance values, and revenue statements from the Settlement Service
  • Webhook notifications for dispatch event activation, cancellation, and meter enrollment updates

Proposed actions

  • Target capability: propose a meter enrollment or market registration refresh request
  • Target capability: propose a capacity nomination or bid for an upcoming dispatch window
  • Target capability: propose an acknowledgment or response payload for an active dispatch event
  • Target capability: propose an interval telemetry batch upload to verify curtailment compliance
  • Target capability: propose registering a webhook subscription endpoint for real-time dispatch alerts

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Curtail flexible loads during grid emergencies

    When Leap signals a dispatch event, the operator identifies flexible HVAC and EV loads and proposes curtailment actions before the event window opens.

    With Event Response, Peak Demand

  • Nominate battery capacity for peak demand windows

    Review battery charge state against forecasted wholesale prices and propose hourly market nominations to capture demand response revenue.

    With Battery Dispatch, Price Shift

  • Reconcile curtailment performance against baseline

    Compare interval telemetry against Leap baseline calculations and propose adjustments to site operations to meet contracted capacity targets.

    With Bill Reconcile

Requirements

  • A Leap developer account with approved market access agreements in target ISO or RTO regions
  • Valid utility meter identifiers and customer consent documentation for enrolled facilities
  • Network endpoints configured to ingest dispatch event notifications with predictable latency
  • Meters equipped with interval data recording capability matching market settlement intervals
Authentication
API key authentication passed via Authorization Bearer headers issued through the Leap developer portal.

Limits

  • Market registration approval requires validation by regional grid operators before meters can bid
  • API request rate limits apply per developer account with standard backoff on concurrent requests
  • Dispatch event response windows are bound by strict market timing rules specific to each program
  • Settlement data availability depends on utility meter data reconciliation timelines

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Leap API ↗

Questions and answers

Which electricity markets does the Leap API support?
Leap connects distributed energy resources to wholesale markets across North America, including CAISO, ERCOT, PJM, NYISO, and ISO New England. Availability of specific capacity, energy, and ancillary services programs depends on regional utility territories and market rules.
How does Fibric receive dispatch notifications?
Notifications arrive through Leap webhook subscriptions or persistent polling of the Program Dispatch and Resource Dispatch endpoints. Incoming events detail start times, duration, target capacity, and participating meter groups.
Can Fibric execute load shedding automatically?
No. Fibric proposes load reductions, battery discharge schedules, or thermostat setbacks for review. An authorized operator approves the plan before control instructions reach local equipment.
Ask about Leap API

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Leap API through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy