Reference · built on requestCommons signalEnergy & grid

REData API

Spanish system data from Red Eléctrica as JSON: balance, demand, generation, exchanges, transmission and markets.

Request accessPricing ↗

About

REData is the open data service of Red Eléctrica, the Spanish transmission system operator. Its API at apidatos.ree.es serves the series behind the REData portal as JSON:API documents: electricity balance, demand, generation, international exchanges, transmission quality and market indicators. Each call names a category and a widget, such as /en/datos/demanda/demanda-tiempo-real, and carries start_date, end_date and a time_trunc of hour, day, month or year. Regional series are selected with geo_trunc, geo_limit and geo_ids, from the peninsular and island systems down to autonomous communities.

An operator reads the generation mix or the market price series for your region and proposes when to move flexible load. You approve each change and keep the receipt.

This is a reference listing. It documents what Fibric would read from REData API 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

  • demanda-tiempo-real, demanda-maxima-diaria, demanda-maxima-horaria and potencia-maxima-instantanea under /datos/demanda
  • estructura-generacion, estructura-renovables, estructura-generacion-emisiones-asociadas and potencia-instalada under /datos/generacion
  • precios-mercados-tiempo-real, componentes-precio and coste-servicios-ajuste under /datos/mercados
  • francia-frontera, portugal-frontera, marruecos-frontera, andorra-frontera and enlace-baleares exchanges under /datos/intercambios, physical and scheduled
  • balance-electrico under /datos/balance, aggregated by hour, day, month or year through time_trunc
  • energia-no-suministrada-ens, tiempo-interrupcion-medio-tim and indice-disponibilidad transmission quality series under /datos/transporte

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

  • Shift flexible load into the renewable hours

    Read estructura-generacion by hour for the peninsular system. The operator proposes moving flexible loads into the hours where renewable output is highest, for your approval, and records the mix it used.

    With Carbon Window

  • Defer a run when the market price climbs

    Pull precios-mercados-tiempo-real by hour. When the price for the coming hours rises above your threshold, the operator proposes deferring a deferrable run and shows the hourly values behind it.

    With Price Shift

  • Watch national demand against your own peak

    Poll demanda-tiempo-real, which returned five-minute forecast points when tested. The operator proposes a pre-cool or shed plan for your site before the system peak. You approve.

    With Peak Demand

Requirements

  • start_date and end_date in ISO 8601 (YYYY-MM-DDTHH:MM) and a time_trunc of hour, day, month or year on every call
  • Accept and Content-Type headers set to application/json
  • For a regional series, geo_trunc=electric_system with geo_limit and geo_ids sent together (for example 8741 for Península)
  • A client that reads JSON:API documents: a data object plus included series with values arrays
Authentication
No key. The API page documents no authentication; apidatos.ree.es answered a plain HTTPS GET with JSON headers when tested.

Limits

  • Regional requests need geo_trunc, geo_limit and geo_ids together; the API page says all three must be sent
  • No rate limits, quotas or maximum date ranges are documented; errors return a status code and a detail message
  • The legal notice limits reuse to informational, non-commercial publication with the source and last-update date cited
  • Widget slugs are Spanish on both the /es/ and /en/ paths

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 REData API ↗

Questions and answers

Do I need an API key for REData?
No. The API page documents no key or login. Send Accept and Content-Type headers of application/json with start_date, end_date and time_trunc. A plain GET to apidatos.ree.es answered with a JSON:API document when tested.
Can I use REData series commercially?
Red Eléctrica's legal notice permits a personal copy and publication for information only, not for commercial purposes, with the Company cited as source together with the date of the latest update. Any other reproduction, extraction or reuse needs written authorisation from Red Eléctrica.
How do I request one region?
Send geo_trunc=electric_system, a geo_limit (peninsular, canarias, baleares, ceuta, melilla or ccaa) and the matching geo_ids: 8741 Península, 8742 Canarias, 8743 Baleares, 8744 Ceuta, 8745 Melilla, or 1 to 19 for an autonomous community. The API page says all three parameters must be sent for a regional request.
Ask about REData API

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This Commons signal listing is developed, published, and supported by Fibric. It reads public data published by Red Eléctrica (apidatos.ree.es). Upstream agencies and projects are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy