Reference · built on requestCommons signalEnergy & grid

RTE Data Portal

RTE's APIs for the French power system: actual and forecast generation, consumption, the Ecowatt signal, prices, and cross-border flows.

About

API Data RTE is the developer portal of RTE, the French electricity transmission system operator. Its catalogue is grouped into Generation, Consumption, Market, Exchanges, and Partners, and each API is versioned and documented with its own user guide. Calls go to digital.iservices.rte-france.com with an OAuth 2.0 bearer token that you obtain after creating an account and declaring an application.

An operator on Fibric subscribes to the APIs you need, for example Consumption and Ecowatt, and proposes a curtailment plan for your French sites when the Ecowatt signal tightens. You approve the plan; the signal values are attached to the receipt.

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

Inputs

  • Actual Generation v1.1: actual_generations_per_production_type and actual_generations_per_unit, hourly, and generation_mix_15min_time_scale at 15-minute intervals
  • Actual Generation water_reserves: weekly fill rates of reservoir and lake hydro storage in MWh, reported by generators
  • Generation Forecast v3.1: D-3, D-2, D-1, and intraday forecasts in MW for France aggregated, wind, solar, and purchase-obligation facilities
  • Consumption v1.2: French consumption in real time and its forecasts, which include grid losses and exclude pumping at hydro plants
  • Ecowatt v5.0: the Ecowatt signal on the state of the French electricity supply
  • Wholesale Market v2.0: prices and hourly volumes from EPEX SPOT and Nord Pool hubs, plus the Signal API's Peak Period notice on D-2 or D-1
  • Exchanges: Physical Flow v1.0 across interconnection lines, Exchange Schedule, Ntc forecasts, Cross Zonal Capacity, and Unavailability Additional Information v7.0

Proposed actions

Read-only. This feed informs operators; it changes nothing.

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

What you can build

  • Turn an Ecowatt alert into a curtailment plan

    Read the Ecowatt signal and the consumption forecast, and draft a load-shedding window for your French sites checked against meters and equipment state. You approve before anything changes.

    With Event Response

  • Pre-cool before the Peak Period signal

    When the Signal API issues a Peak Period notice on D-2 or D-1, propose pre-cooling and staged loads for the flagged hours within comfort limits.

    With Peak Demand

  • Schedule the battery on French hub prices

    Combine Wholesale Market prices with the site load forecast and battery state of charge, and propose tomorrow's charge and discharge blocks for sign-off.

    With Battery Dispatch, Price Shift

Requirements

  • An account on data.rte-france.com and one declared application, with a subscription to each API you read
  • Date parameters in the form YYYY-MM-DDThh:mm:sszzzzzz with the time zone included
  • A retry that honours the Retry-After header on HTTP 429
  • The source named wherever public data is reused, as the general terms require
Authentication
OAuth 2.0. You create a free account, declare an application on the portal to receive token-type client logins, and send the resulting token as Authorization: Bearer on each call.

Limits

  • Each organisation has a maximum number of calls; exceeding it returns HTTP 429, and RTE advises one call per hour for the hourly generation resources
  • Period caps per resource: 155 days for generation by production type, 7 days per unit, 366 days for water reserves and the 15-minute mix
  • A response over 7 MB returns HTTP 413 and a URI over 2048 characters returns HTTP 414
  • EPEX SPOT and Nord Pool figures in the Wholesale Market API are for internal use; commercial reuse needs their written consent

Access and pricing

Reference listing. Public feed access is separate from Fibric integration. If you request this feed, your quote covers the build, usage, and support.

Request RTE Data Portal ↗

Questions and answers

How do you authenticate against the RTE APIs?
With OAuth 2.0. After creating an account you declare an application on the Data Portal and receive token-type connection logins, which you can reset yourself. Each request carries the token in an Authorization: Bearer header. A 401 means the token is missing or expired.
Is there a call quota?
Yes. The user guide describes a check that the caller's organisation has not exceeded its maximum number of authorised calls; if it has, the API returns HTTP 429 with a Retry-After header in seconds. RTE also recommends one call per hour for the hourly Actual Generation resources.
Can you reuse the data?
Public data may be reused provided the source is mentioned, under the portal's general terms. Power exchange data from EPEX SPOT and Nord Pool is their property and may be used internally only; commercial use or derivative instruments need their written consent.
Ask about RTE Data Portal

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.