Marine Weather is a simple tool for getting marine weather data. It returns the current weather conditions in coordinates within the ocean and sea.
Try it — live request, no key required
No key required to try it. Get a key to use it in your app.
{
"status": "ok",
"error": null,
"data": {
// Marine Weather response payload
}
}
About the Marine Weather API
Marine Weather works by retrieving the marine weather data from various reliable weather sources and providing it in a structured format. You can expect accurate and up-to-date information.
What people use it for
- Marine Navigation
- Navigate the seas by using the Marine Weather API to get marine weather data. Use the data to plan routes and avoid hazardous weather conditions
- Fishing Forecast
- Forecast fishing conditions by using the Marine Weather API to get marine weather data. Use the data to predict fish behavior and plan fishing trips
- Boating Safety
- Ensure boating safety by using the Marine Weather API to get marine weather data. Use the data to monitor weather conditions and make informed decisions on boating activities
- Ocean Research
- Conduct ocean research by using the Marine Weather API to get marine weather data. Use the data to study weather patterns and their impact on marine ecosystems
Ways to call it
One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.
- JSON
- Default REST response
- XML
- Markup format
- YAML
- Human-readable
- CSV
- Tabular export
- GraphQL
- Query language
- MCP
- For AI agents
Other ways to use Marine Weather
Same data, same APIVerve account, same credit balance — one key works on all of them.
What does the Marine Weather API do?
How do I authenticate Marine Weather API requests?
How much does the Marine Weather API cost?
How fast is the Marine Weather API?
What response formats does the Marine Weather API support?
What HTTP method does the Marine Weather API use?
Request parameters — GET /v1/marineweather
Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.
Required
| Parameter | Type | Example | Description |
|---|---|---|---|
latRequired | number | 29.48003 | The latitude coordinate of the location range -90-90 |
lonRequired | number | -37.62424 | The longitude coordinate of the location range -180-180 |
curl "https://api.apiverve.com/v1/marineweather?lat=29.48003&lon=-37.62424" \
-H "x-api-key: YOUR_API_KEY"Authentication
Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.
| Header | When | Value |
|---|---|---|
x-api-keyRequired | Every request | Your API key. Header names are case-insensitive, so X-API-Key is the same header. |
AuthorizationAlternate | Instead of the above | Bearer <key> — for clients that only expose bearer auth. Resolves to the same account and the same billing. |
A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.
Response — GET /v1/marineweather
Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.
{
"status": "ok",
"error": null,
"data": {
"location": {
"lat": 29.48003,
"lon": -37.62424
},
"weather": {
"maxtempc": 22.9,
"maxtempf": 73.2,
"mintempc": 21.8,
"mintempf": 71.2,
"avgtempc": 22.5,
"avgtempf": 72.5,
"maxwindmph": 11.1,
"maxwindkph": 17.9,
"totalprecipmm": 3.29,
"totalprecipin": 0.13,
"totalsnowcm": 0,
"avgviskm": 9.9,
"avgvismiles": 6,
"moonphase": "Waning Crescent",
"moonillumination": 16
}
}
}
Response fields
Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.
| Field | Type | Example | Description |
|---|---|---|---|
location | object | {...} | |
lat | number | 29.48003 | Latitude coordinate of the marine weather location |
lon | number | -37.62424 | Longitude coordinate of the marine weather location |
weather | object | {...} | |
maxtempc | number | 22.9 | Maximum temperature in Celsius for the location |
maxtempf | number | 73.2 | Maximum temperature in Fahrenheit for the location |
mintempc | number | 21.8 | Minimum temperature in Celsius for the location |
mintempf | number | 71.2 | Minimum temperature in Fahrenheit for the location |
avgtempc | number | 22.5 | Average temperature in Celsius for the location |
avgtempf | number | 72.5 | Average temperature in Fahrenheit for the location |
maxwindmph | number | 11.1 | Maximum wind speed in miles per hour |
maxwindkph | number | 17.9 | Maximum wind speed in kilometers per hour |
totalprecipmm | number | 3.29 | Total precipitation amount in millimeters |
totalprecipin | number | 0.13 | Total precipitation amount in inches |
totalsnowcm | number | 0 | Total snow depth in centimeters |
avgviskmPremium | number | 9.9 | Average visibility distance in kilometers |
avgvismilesPremium | number | 6 | Average visibility distance in miles |
moonphasePremium | string | "Waning Crescent" | Current moon phase description for the location |
moonilluminationPremium | number | 16 | Moon illumination percentage from zero to one hundred |
Response headers
Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.
| Header | What it carries |
|---|---|
x-api-remaining-credits | Credits left in the current cycle |
x-api-credits-used | Credits spent in the current cycle |
x-api-max-credits | The cycle's allowance |
x-api-version | Version of the endpoint that answered |
Errors
Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.
| Status | Meaning | What to do |
|---|---|---|
400 | Input was rejected | Read error; it names the parameter that has to change. |
401 | Key missing or invalid | Check the header name and the key value. |
403 | Key valid, but not permitted here | A key restriction or an IP allow-list — never a bad key. |
429 | Rate limited, or out of credits | Read error to tell them apart, then back off or top up. |
What a call costs — 10 credits per call
Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.
| Plan | Per month | Credits | Marine Weather calls | Per 1,000 calls |
|---|---|---|---|---|
| Free | Free | 200 | 20 | Free |
| Starter | $29.99 | 200,000 | 20,000 | $1.50 |
| Pro | $99.99 | 1,000,000 | 100,000 | $1.00 |
| Mega | $299.99 | 4,000,000 | 400,000 | $0.75 |
Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.
Call it from cURL — GET /v1/marineweather
No SDK to install — this is a plain HTTPS call to /v1/marineweather with your key in the x-api-key header. Swap in a real key and it runs as-is.
curl "https://api.apiverve.com/v1/marineweather" \
-H "x-api-key: YOUR_API_KEY"Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Node.js — GET /v1/marineweather
Install the Node.js SDK, then call the Marine Weather API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
npm install @apiverve/marineweatherconst res = await fetch("https://api.apiverve.com/v1/marineweather", {
headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Python — GET /v1/marineweather
Install the Python SDK, then call the Marine Weather API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
pip install apiverve-marineweatherimport requests
res = requests.get(
"https://api.apiverve.com/v1/marineweather",
headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from C# / .NET — GET /v1/marineweather
Install the C# / .NET SDK, then call the Marine Weather API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
dotnet add package APIVerve.API.MarineWeatherusing var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");
var json = await client.GetStringAsync("https://api.apiverve.com/v1/marineweather");
Console.WriteLine(json);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Go — GET /v1/marineweather
No SDK to install — this is a plain HTTPS call to /v1/marineweather with your key in the x-api-key header. Swap in a real key and it runs as-is.
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/marineweather", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")
res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from PHP — GET /v1/marineweather
No SDK to install — this is a plain HTTPS call to /v1/marineweather with your key in the x-api-key header. Swap in a real key and it runs as-is.
$ch = curl_init("https://api.apiverve.com/v1/marineweather");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);
$response = curl_exec($ch);
echo $response;Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Ruby — GET /v1/marineweather
No SDK to install — this is a plain HTTPS call to /v1/marineweather with your key in the x-api-key header. Swap in a real key and it runs as-is.
require "net/http"
uri = URI("https://api.apiverve.com/v1/marineweather")
req = Net::HTTP::Get.new(uri)
req["x-api-key"] = "YOUR_API_KEY"
res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.bodyResources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Zero-code embed — one snippet, no backend
Drop an interactive Marine Weather form onto any page. The widget calls the API for you, so no key ever appears in your markup and there is nothing to deploy.
Changelog — Marine Weather API
Every change to this endpoint, newest first. Breaking changes ship as a new version and the previous one keeps serving — response fields are added, never removed or retyped in place, so an integration written against v1 keeps working.
Entries are picked up from dated catalog snapshots, so the first one appears after the next snapshot that moves something. A period where nothing changed produces no entry — silence is a valid changelog.
Weather
- Air Quality
- Marine Weather
- Moonrise Moonset
- Solar Potential
- Sunrise Sunset
- Weather
- Weather Seasons
- Worldwide Earthquakes
Related articles
All articles →
Building Health-Conscious Apps With Air Quality DataAir quality affects millions of users. Here's how to integrate environmental health data meaningfully.Read
API Caching: The Cheapest Performance WinEvery duplicate API call is wasted money. Here's how to cache responses properly—and when not to.Read
Weather APIs: Build a Dashboard That's Actually UsefulCurrent conditions, forecasts, air quality, sunrise times—here's how to build a weather dashboard users will love.Read