# Open-Meteo Flood Forecast API

> Daily river discharge forecast and history for any coordinates from the GloFAS flood model.

Source: https://www.sandbase.ai/apis/open-meteo/flood
API reference: https://www.sandbase.ai/apis/open-meteo/flood/docs

## Facts

- Provider: Open-Meteo
- Type: Data API
- Endpoint: `POST https://api.sandbase.ai/v1/api/open-meteo/flood`
- Price: $0.0001 per call
- Free allowance: 100 calls per organization per UTC day, shared across eligible APIs
- Capabilities: api, open meteo, weather
- Billing: pay per use from one SandBase balance; no provider account or subscription needed

## Call it

`POST https://api.sandbase.ai/v1/api/open-meteo/flood` with `Authorization: Bearer $SANDBASE_API_KEY` and the parameters as a JSON body.

| Parameter | Type | Required | Allowed values |
| --- | --- | --- | --- |
| `latitude` | string | yes |  |
| `longitude` | string | yes |  |
| `cell_selection` | string | no | land, sea, nearest |
| `daily` | string | no |  |
| `end_date` | string | no |  |
| `ensemble` | boolean | no |  |
| `forecast_days` | integer | no |  |
| `models` | string | no |  |
| `past_days` | integer | no |  |
| `start_date` | string | no |  |
| `timeformat` | string | no | iso8601, unixtime |

## FAQ

### How do I use the Open-Meteo Flood Forecast API?

Send a POST request to https://api.sandbase.ai/v1/api/open-meteo/flood with your SandBase API key in the Authorization header (Bearer) and the parameters as a JSON body. You can also try it in the Playground on this page without writing code.

### How much does the Open-Meteo Flood Forecast API cost?

$0.0001 per call. Every organization gets 100 free calls per UTC day, shared across eligible SandBase APIs including this one; after that each call is billed at this price from your SandBase balance. There is no subscription.

### What parameters does the Open-Meteo Flood Forecast API accept?

Required: latitude (string) and longitude (string). Optional: cell_selection (one of land, sea, nearest), daily (string), end_date (string), ensemble (boolean), forecast_days (integer) and models (string) and 3 more. The Parameters table and the Playground on this page list every field.

### What does the Open-Meteo Flood Forecast API return?

A JSON response returned in the same HTTP request (synchronous).

### Do I need a Open-Meteo developer account or API key?

No. Open-Meteo Flood Forecast runs through SandBase, so one SandBase API key covers this endpoint and every other API and model in the catalog. You do not need to apply for Open-Meteo API access separately.

## README

### Open-Meteo Flood Forecast API

Daily river discharge forecast and history for any coordinates from the GloFAS flood model.

The result is returned in `outputs[0].data` as the official Open-Meteo API response, unchanged.

#### Request

```bash
curl -X POST "https://api.sandbase.ai/v1/api/open-meteo/flood" \
  -H "Authorization: Bearer $SANDBASE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"latitude": "52.52", "longitude": "13.41", "daily": "river_discharge"}'
```

#### Parameters

| Name | Type | Required | Description |
|---|---|---|---|
| `cell_selection` | string | No | Grid-cell preference for the coordinate. Default `nearest`. |
| `daily` | string | No | Comma-separated list of daily aggregation variables to return. Requires `timezone`. Common values: `river_discharge`, `river_discharge_mean`, `river_discharge_m |
| `end_date` | string | No | End of the interval, `yyyy-mm-dd` (ISO 8601). |
| `ensemble` | boolean | No | Return all ensemble members instead of the aggregate. Default `false`. |
| `forecast_days` | integer | No | Number of forecast days to return (0-210). Default 92. |
| `latitude` | string | Yes | WGS84 latitude of the location. Multiple coordinates can be comma-separated. |
| `longitude` | string | Yes | WGS84 longitude of the location (negative for the Americas). Multiple coordinates can be comma-separated. |
| `models` | string | No | Comma-separated GloFAS models. Default best match. |
| `past_days` | integer | No | Number of past days to include (0-92). Default 0. |
| `start_date` | string | No | Start of the interval, `yyyy-mm-dd` (ISO 8601). |
| `timeformat` | string | No | Time output format. Default `iso8601`. |

#### Pricing

Flat price per call. Failed calls are not charged.