Reference · built on requestCommons signalWeather & climate

Météo-France API portal

French vigilance bulletins, station observations, radar, and AROME and ARPEGE model fields from the Météo-France API portal.

Request accessPricing ↗

About

Météo-France runs its API portal at portail-api.meteofrance.fr. Each API is subscribed to separately: AROME and ARPEGE model fields, AROME-PI nowcasts, DonneesPubliquesObservation for station readings, DonneesPubliquesVigilance for the departmental danger level, DonneesPubliquesRadar, and DonneesPubliquesClimatologie. The same datasets are published in bulk on data.gouv.fr under the Licence Ouverte 2.0.

On Fibric, an operator reads the vigilance level and the observations for your French sites and proposes a hold, a notice, or a schedule change for your approval, with the bulletin attached.

This is a reference listing. It documents what Fibric would read from Météo-France API 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

  • Vigilance report and map products as JSON for day D and D+1 from DonneesPubliquesVigilance, by department
  • Observations at 6-minute or hourly steps for the last 24 hours from DonneesPubliquesObservation, across over 2,000 French stations
  • AROME and ARPEGE analysis and forecast fields as GRIB2, GeoTIFF, or PNG, with WMS GetCapabilities on the AROME API
  • Radar data at 5-minute frequency by station or as France and overseas mosaics from DonneesPubliquesRadar
  • Climatological series per station at 6-minute, hourly, daily, decadal, and monthly steps as CSV from DonneesPubliquesClimatologie
  • Ensemble runs from PE-AROME and PE-ARPEGE, and forest fire danger from DonneesPubliquesMeteoForets

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

  • Hold French deliveries at your vigilance trigger

    Read the vigilance map product for the departments you ship to. When a department reaches the level you set, the operator proposes holding the affected orders and drafts the customer notice.

    With Weather Hold

  • Warn crews before a heat episode

    Combine the vigilance bulletin with the hourly observations near each site. When both cross your trigger, the operator proposes a notice to crew leads and attaches the bulletin text.

    With Severe Weather Notice

  • Set the morning start from local readings

    Use the 6-minute observations and AROME fields around each site to time plant start. The operator proposes the start time and records the reading it used.

    With Optimal Start

Requirements

  • A portal account and a subscription to every API you will call, made before the token is generated
  • The department codes and station ids for your French sites
  • Token renewal logic if you use OAuth2; the portal FAQ describes renewal every hour
  • A GRIB2 reader if you use AROME or ARPEGE fields rather than observations
Authentication
A portal account and a free subscription to each API, then an API key sent in the apikey header or an OAuth2 client-credentials token sent as a Bearer.

Limits

  • Each API has its own throttling tier: 50 requests per minute for AROME and climatology, 100 for observations, 60 for vigilance
  • A token covers only the APIs subscribed before it was generated; a new subscription needs a new token
  • The observation API covers the last 24 hours only; older readings come from the climatology API or data.gouv.fr files
  • Portal labels and most API descriptions are in French

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 Météo-France API portal ↗

Questions and answers

Is the portal free to use?
The public APIs in the catalogue are marked as not paid. You create an account with a username and email, subscribe to each API for free, and generate a token. Throttling tiers per API cap the requests per minute.
API key or OAuth2?
Both are offered. The API key is a JWT sent in the apikey header or as a query parameter. OAuth2 uses client credentials against portail-api.meteofrance.fr/token and a Bearer header; the FAQ describes hourly renewal and gives a Python example.
Where are the bulk files?
On data.gouv.fr under the Météo-France organisation: Données climatologiques de base at 6-minute, hourly, daily, and monthly steps as compressed CSV, plus AROME and ARPEGE packages. They carry the Licence Ouverte / Open Licence version 2.0.
Ask about Météo-France API portal

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 Météo-France (portail-api.meteofrance.fr, public-api.meteofrance.fr). 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