latitudestringrequired
WGS84 latitude of the location. Multiple coordinates can be comma-separated.
Open-Meteo Flood Forecast
https://api.sandbase.ai/v1/api/open-meteo/floodDaily river discharge forecast and history for any coordinates from the GloFAS flood model.
- Price
- $0.0001USD / call
- Method
- POST
- Response
- JSON
- Parameters
- 2 required · 9 optional
100 free calls / dayFirst 100 calls per day free (shared per organization) · Resets at 00:00 UTC. Pay per call after that.
Playground
Input
WGS84 latitude of the location. Multiple coordinates can be comma-separated.
WGS84 longitude of the location (negative for the Americas). Multiple coordinates can be comma-separated.
Grid-cell preference for the coordinate. Default `nearest`. Allowed values: land, sea, nearest.
Comma-separated list of daily aggregation variables to return. Requires `timezone`. Common values: `river_discharge`, `river_discharge_mean`, `river_discharge_median`, `river_discharge_max`, `river_discharge_min`, `river_discharge_p25`, `river_discharge_p75`.
End of the interval, `yyyy-mm-dd` (ISO 8601).
Return all ensemble members instead of the aggregate. Default `false`.
Number of forecast days to return (0-210). Default 92.
Comma-separated GloFAS models. Default best match.
Number of past days to include (0-92). Default 0.
Start of the interval, `yyyy-mm-dd` (ISO 8601).
Time output format. Default `iso8601`. Allowed values: iso8601, unixtime.
OutputReady
Your output will appear here
Complete the inputs, then click Run.
API 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
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.
Start building
Send your first request
Platform API endpoint with unified authentication and usage tracking.
# The quoted heredoc keeps Unicode and shell metacharacters unchanged.
result=$(curl --fail-with-body --silent \
-X POST "https://api.sandbase.ai/v1/api/open-meteo/flood" \
-H "Authorization: Bearer $SANDBASE_API_KEY" \
-H "Content-Type: application/json" \
--data-binary @- <<'SANDBASE_JSON'
{
"daily": "river_discharge",
"models": "seamless_v4",
"end_date": "2024-01-07",
"ensemble": false,
"latitude": "52.52",
"longitude": "13.41",
"past_days": 0,
"start_date": "2024-01-01",
"timeformat": "iso8601",
"forecast_days": 7,
"cell_selection": "nearest"
}
SANDBASE_JSON
)
printf '%s\n' "$result"2. Authentication
Set your SandBase API key in your server environment. Requests use Bearer authentication.
export SANDBASE_API_KEY="YOUR_API_KEY"Keep your key on the server. Do not expose it in browser code.
3. Parameters
longitudestringrequired
WGS84 longitude of the location (negative for the Americas). Multiple coordinates can be comma-separated.
cell_selectionstring
Grid-cell preference for the coordinate. Default `nearest`.
Default: "nearest"
Possible values: land, sea, nearest
dailystring
Comma-separated list of daily aggregation variables to return. Requires `timezone`. Common values: `river_discharge`, `river_discharge_mean`, `river_discharge_median`, `river_discharge_max`, `river_discharge_min`, `river_discharge_p25`, `river_discharge_p75`.
end_datestring
End of the interval, `yyyy-mm-dd` (ISO 8601).
ensembleboolean
Return all ensemble members instead of the aggregate. Default `false`.
Default: false
forecast_daysinteger
Number of forecast days to return (0-210). Default 92.
Default: 92
modelsstring
Comma-separated GloFAS models. Default best match.
past_daysinteger
Number of past days to include (0-92). Default 0.
Default: 0
start_datestring
Start of the interval, `yyyy-mm-dd` (ISO 8601).
timeformatstring
Time output format. Default `iso8601`.
Default: "iso8601"
Possible values: iso8601, unixtime
4. Response
Saved example response for this API; no live request is made when viewing it.
No saved response has been published. Run the API in Playground to inspect its response.
Explore more
Related APIs
| API | Price | Response |
|---|---|---|
Open-Meteo Flood ForecastThis API Open-Meteo | $0.0001 per call | JSON |
Open-Meteo | $0.0001 per call | JSON |
Open-Meteo | $0.0001 per call | JSON |
Open-Meteo | $0.0001 per call | JSON |
Open-Meteo | $0.0001 per call | JSON |
Open-Meteo | $0.0001 per call | JSON |
Questions
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.