latitudestringrequired
WGS84 latitude of the location. Multiple coordinates can be comma-separated.
https://api.sandbase.ai/v1/api/open-meteo/marineHourly and daily marine forecast by coordinates: wave height, direction and period, swell and ocean currents.
Your output will appear here
Complete the inputs, then click Run.
Hourly and daily marine forecast by coordinates: wave height, direction and period, swell and ocean currents.
The result is returned in outputs[0].data as the official Open-Meteo API response, unchanged.
curl -X POST "https://api.sandbase.ai/v1/api/open-meteo/marine" \
-H "Authorization: Bearer $SANDBASE_API_KEY" \
-H "Content-Type: application/json" \
-d '{"latitude": "54.54", "longitude": "10.23", "hourly": "wave_height", "forecast_days": 1}'
| Name | Type | Required | Description |
|---|---|---|---|
cell_selection | string | No | Grid-cell preference for the coordinate. Default sea. |
current | string | No | Comma-separated list of current-condition variables to return. Same variable set as hourly. |
daily | string | No | Comma-separated list of daily aggregation variables to return. Requires timezone. Common values: wave_height_max, wave_direction_dominant, `wave_period_ma |
end_date | string | No | End of the interval, yyyy-mm-dd (ISO 8601). |
forecast_days | integer | No | Number of forecast days to return (0-8). Default 5. |
hourly | string | No | Comma-separated list of hourly variables to return. Common values: wave_height, wave_direction, wave_period, wind_wave_height, wind_wave_direction, `w |
latitude | string | Yes | WGS84 latitude of the location. Multiple coordinates can be comma-separated. |
length_unit | string | No | Unit for wave heights. Default metric. |
longitude | string | Yes | WGS84 longitude of the location (negative for the Americas). Multiple coordinates can be comma-separated. |
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. |
timezone | string | No | IANA time zone name (e.g. Europe/Berlin) or auto to resolve from coordinates. Defaults to GMT. |
Flat price per call. Failed calls are not charged.
Start building
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/marine" \
-H "Authorization: Bearer $SANDBASE_API_KEY" \
-H "Content-Type: application/json" \
--data-binary @- <<'SANDBASE_JSON'
{
"daily": "wave_height_max",
"hourly": "wave_height",
"current": "wave_height,wave_period",
"end_date": "2024-01-07",
"latitude": "54.54",
"timezone": "Europe/Berlin",
"longitude": "10.23",
"past_days": 0,
"start_date": "2024-01-01",
"timeformat": "iso8601",
"length_unit": "metric",
"forecast_days": 1,
"cell_selection": "sea"
}
SANDBASE_JSON
)
printf '%s\n' "$result"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.
latitudestringrequiredWGS84 latitude of the location. Multiple coordinates can be comma-separated.
longitudestringrequiredWGS84 longitude of the location (negative for the Americas). Multiple coordinates can be comma-separated.
cell_selectionstringGrid-cell preference for the coordinate. Default `sea`.
Default: "sea"
Possible values: land, sea, nearest
currentstringComma-separated list of current-condition variables to return. Same variable set as `hourly`.
dailystringComma-separated list of daily aggregation variables to return. Requires `timezone`. Common values: `wave_height_max`, `wave_direction_dominant`, `wave_period_max`, `wind_wave_height_max`, `swell_wave_height_max`.
end_datestringEnd of the interval, `yyyy-mm-dd` (ISO 8601).
forecast_daysintegerNumber of forecast days to return (0-8). Default 5.
Default: 5
hourlystringComma-separated list of hourly variables to return. Common values: `wave_height`, `wave_direction`, `wave_period`, `wind_wave_height`, `wind_wave_direction`, `wind_wave_period`, `swell_wave_height`, `swell_wave_direction`, `swell_wave_period`, `ocean_current_velocity`, `ocean_current_direction`, `se
length_unitstringUnit for wave heights. Default `metric`.
Default: "metric"
Possible values: metric, imperial
past_daysintegerNumber of past days to include (0-92). Default 0.
Default: 0
start_datestringStart of the interval, `yyyy-mm-dd` (ISO 8601).
timeformatstringTime output format. Default `iso8601`.
Default: "iso8601"
Possible values: iso8601, unixtime
timezonestringIANA time zone name (e.g. `Europe/Berlin`) or `auto` to resolve from coordinates. Defaults to `GMT`.
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
| API | Price | Response |
|---|---|---|
Open-Meteo Marine 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
Send a POST request to https://api.sandbase.ai/v1/api/open-meteo/marine 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.
$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.
Required: latitude (string) and longitude (string). Optional: cell_selection (one of land, sea, nearest), current (string), daily (string), end_date (string), forecast_days (integer) and hourly (string) and 5 more. The Parameters table and the Playground on this page list every field.
A JSON response returned in the same HTTP request (synchronous).
No. Open-Meteo Marine 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.