Marine Weather API
Marine Weather is a simple tool for getting marine weather data. It returns the current weather conditions in coordinates within the ocean and sea.
The Marine Weather API provides reliable and fast access to marine weather data through a simple REST interface. Built for developers who need consistent, high-quality results with minimal setup time.
To use Marine Weather, you need an API key. You can get one by creating a free account and visiting your dashboard.
GET Endpoint
https://api.apiverve.com/v1/marineweatherCode Examples
Here are examples of how to call the Marine Weather API in different programming languages:
curl -X GET \
"https://api.apiverve.com/v1/marineweather?lat=29.48003&lon=-37.62424" \
-H "X-API-Key: your_api_key_here"const response = await fetch('https://api.apiverve.com/v1/marineweather?lat=29.48003&lon=-37.62424', {
method: 'GET',
headers: {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
}
});
const data = await response.json();
console.log(data);import requests
headers = {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
}
response = requests.get('https://api.apiverve.com/v1/marineweather?lat=29.48003&lon=-37.62424', headers=headers)
data = response.json()
print(data)const https = require('https');
const url = require('url');
const options = {
method: 'GET',
headers: {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
}
};
const req = https.request('https://api.apiverve.com/v1/marineweather?lat=29.48003&lon=-37.62424', options, (res) => {
let data = '';
res.on('data', (chunk) => data += chunk);
res.on('end', () => console.log(JSON.parse(data)));
});
req.end();<?php
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, 'https://api.apiverve.com/v1/marineweather?lat=29.48003&lon=-37.62424');
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_CUSTOMREQUEST, 'GET');
curl_setopt($ch, CURLOPT_HTTPHEADER, [
'X-API-Key: your_api_key_here',
'Content-Type: application/json'
]);
$response = curl_exec($ch);
curl_close($ch);
$data = json_decode($response, true);
print_r($data);
?>package main
import (
"fmt"
"io"
"net/http"
)
func main() {
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/marineweather?lat=29.48003&lon=-37.62424", nil)
req.Header.Set("X-API-Key", "your_api_key_here")
req.Header.Set("Content-Type", "application/json")
client := &http.Client{}
resp, err := client.Do(req)
if err != nil {
panic(err)
}
defer resp.Body.Close()
body, _ := io.ReadAll(resp.Body)
fmt.Println(string(body))
}require 'net/http'
require 'json'
uri = URI('https://api.apiverve.com/v1/marineweather?lat=29.48003&lon=-37.62424')
http = Net::HTTP.new(uri.host, uri.port)
http.use_ssl = true
request = Net::HTTP::Get.new(uri)
request['X-API-Key'] = 'your_api_key_here'
request['Content-Type'] = 'application/json'
response = http.request(request)
puts JSON.pretty_generate(JSON.parse(response.body))using System;
using System.Net.Http;
using System.Text;
using System.Threading.Tasks;
class Program
{
static async Task Main(string[] args)
{
using var client = new HttpClient();
client.DefaultRequestHeaders.Add("X-API-Key", "your_api_key_here");
var response = await client.GetAsync("https://api.apiverve.com/v1/marineweather?lat=29.48003&lon=-37.62424");
response.EnsureSuccessStatusCode();
var responseBody = await response.Content.ReadAsStringAsync();
Console.WriteLine(responseBody);
}
}Authentication
The Marine Weather API requires authentication via API key. Include your API key in the request header:
X-API-Key: your_api_key_hereInteractive API Playground
Test the Marine Weather API directly in your browser with live requests and responses.
Parameters
The following parameters are available for the Marine Weather API:
Get Marine Weather
| Parameter | Type | Required | Description | Default | Example |
|---|---|---|---|---|---|
lat | number | required | The latitude coordinate of the location Range: -90 - 90 | - | |
lon | number | required | The longitude coordinate of the location Range: -180 - 180 | - |
Response
The Marine Weather API returns responses in JSON, XML, YAML, and CSV formats:
Example Responses
{
"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
}
}
}<?xml version="1.0" encoding="UTF-8"?>
<response>
<status>ok</status>
<error xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<data>
<location>
<lat>29.48003</lat>
<lon>-37.62424</lon>
</location>
<weather>
<maxtempc>22.9</maxtempc>
<maxtempf>73.2</maxtempf>
<mintempc>21.8</mintempc>
<mintempf>71.2</mintempf>
<avgtempc>22.5</avgtempc>
<avgtempf>72.5</avgtempf>
<maxwindmph>11.1</maxwindmph>
<maxwindkph>17.9</maxwindkph>
<totalprecipmm>3.29</totalprecipmm>
<totalprecipin>0.13</totalprecipin>
<totalsnowcm>0</totalsnowcm>
<avgviskm>9.9</avgviskm>
<avgvismiles>6</avgvismiles>
<moonphase>Waning Crescent</moonphase>
<moonillumination>16</moonillumination>
</weather>
</data>
</response>
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
| key | value |
|---|---|
| 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 Structure
All API responses follow a consistent structure with the following fields:
| Field | Type | Description | Example |
|---|---|---|---|
status | string | Indicates whether the request was successful ("ok") or failed ("error") | ok |
error | string | null | Contains error message if status is "error", otherwise null | null |
data | object | null | Contains the API response data if successful, otherwise null | {...} |
Learn more about response formats →
Response Data Fields
When the request is successful, the data object contains the following fields:
| Field | Type | Sample Value | Description |
|---|---|---|---|
location | object | - | |
â”” lat | number | Latitude coordinate of the marine weather location | |
â”” lon | number | Longitude coordinate of the marine weather location | |
weather | object | - | |
â”” maxtempc | number | Maximum temperature in Celsius for the location | |
â”” maxtempf | number | Maximum temperature in Fahrenheit for the location | |
â”” mintempc | number | Minimum temperature in Celsius for the location | |
â”” mintempf | number | Minimum temperature in Fahrenheit for the location | |
â”” avgtempc | number | Average temperature in Celsius for the location | |
â”” avgtempf | number | Average temperature in Fahrenheit for the location | |
â”” maxwindmph | number | Maximum wind speed in miles per hour | |
â”” maxwindkph | number | Maximum wind speed in kilometers per hour | |
â”” totalprecipmm | number | Total precipitation amount in millimeters | |
â”” totalprecipin | number | Total precipitation amount in inches | |
â”” totalsnowcm | number | Total snow depth in centimeters | |
â”” avgviskmPremium | number | Average visibility distance in kilometers | |
â”” avgvismilesPremium | number | Average visibility distance in miles | |
â”” moonphasePremium | string | Current moon phase description for the location | |
â”” moonilluminationPremium | number | Moon illumination percentage from zero to one hundred |
Headers
Required and optional headers for Marine Weather API requests:
| Header Name | Required | Example Value | Description |
|---|---|---|---|
X-API-Key | required | your_api_key_here | Your APIVerve API key. Found in your dashboard under API Keys. |
Accept | optional | application/json | Specify response format: application/json (default), application/xml, or application/yaml |
User-Agent | optional | MyApp/1.0 | Identifies your application for analytics and debugging purposes |
X-Request-ID | optional | req_123456789 | Custom request identifier for tracking and debugging requests |
Cache-Control | optional | no-cache | Control caching behavior for the request and response |
GraphQL AccessALPHA
Access Marine Weather through GraphQL to combine it with other API calls in a single request. Query only the marine weather data you need with precise field selection, and orchestrate complex data fetching workflows.
Credit Cost: Each API called in your GraphQL query consumes its standard credit cost.
POST https://api.apiverve.com/v1/graphqlquery {
marineweather(
input: {
lat: 29.48003
lon: -37.62424
}
) {
location {
lat
lon
}
weather {
maxtempc
maxtempf
mintempc
mintempf
avgtempc
avgtempf
maxwindmph
maxwindkph
totalprecipmm
totalprecipin
totalsnowcm
avgviskm
avgvismiles
moonphase
moonillumination
}
}
}Note: Authentication is handled via the x-api-key header in your GraphQL request, not as a query parameter.
CORS Support
The Marine Weather API supports Cross-Origin Resource Sharing (CORS) with wildcard configuration, allowing you to call Marine Weather directly from browser-based applications without proxy servers.
| CORS Header | Value | Description |
|---|---|---|
Access-Control-Allow-Origin | * | Accepts requests from any origin |
Access-Control-Allow-Methods | * | Accepts any HTTP method |
Access-Control-Allow-Headers | * | Accepts any request headers |
Browser Usage: You can call Marine Weather directly from JavaScript running in the browser without encountering CORS errors. No proxy server or additional configuration needed.
Rate Limiting
Marine Weather API requests are subject to rate limiting based on your subscription plan. These limits ensure fair usage and maintain service quality for all Marine Weather users.
| Plan | Rate Limit | Description |
|---|---|---|
| Free | 5 requests/min | Hard rate limit enforced - exceeding will return 429 errors |
| Starter | No Limit | Production ready - standard traffic priority |
| Pro | No Limit | Production ready - preferred traffic priority |
| Mega | No Limit | Production ready - highest traffic priority |
Learn more about rate limiting →
Rate Limit Headers
When rate limits apply, each Marine Weather response includes headers to help you track your usage:
| Header | Description |
|---|---|
X-RateLimit-Limit | Maximum number of requests allowed per time window |
X-RateLimit-Remaining | Number of requests remaining in the current window |
X-RateLimit-Reset | Unix timestamp when the rate limit window resets |
Handling Rate Limits
Free Plan: When you exceed your rate limit, Marine Weather returns a 429 Too Many Requests status code. Your application should implement appropriate backoff logic to handle this gracefully.
Paid Plans: No rate limiting or throttling applied. All paid plans (Starter, Pro, Mega) are production-ready.
Best Practices for Marine Weather:
- Monitor the rate limit headers to track your Marine Weather usage (Free plan only)
- Cache marine weather responses where appropriate to reduce API calls
- Upgrade to Pro or Mega for guaranteed no-throttle Marine Weather performance
Note: Marine Weather rate limits are separate from credit consumption. You may have credits remaining but still hit rate limits when using Marine Weather on Free tier.
Error Codes
The Marine Weather API uses standard HTTP status codes to indicate success or failure:
| Code | Message | Description | Solution |
|---|---|---|---|
200 | OK | Request successful, data returned | No action needed - request was successful |
400 | Bad Request | Invalid request parameters or malformed request | Check required parameters and ensure values match expected formats |
401 | Unauthorized | Missing or invalid API key | Include x-api-key header with valid API key from dashboard |
403 | Forbidden | API key lacks permission or insufficient credits | Check credit balance in dashboard or upgrade plan |
429 | Too Many Requests | Rate limit exceeded (Free: 5 req/min) | Implement request throttling or upgrade to paid plan |
500 | Internal Server Error | Server error occurred | Retry request after a few seconds, contact support if persists |
503 | Service Unavailable | API temporarily unavailable | Wait and retry, check status page for maintenance updates |
Learn more about error handling →
Need help? Contact support with your X-Request-ID for assistance.
Integrate Marine Weather with SDKs
Get started quickly with official Marine Weather SDKs for your preferred language. Each library handles authentication, request formatting, and error handling automatically.
Available for Node.js, Python, C#/.NET, and Android/Java. All SDKs are open source and regularly updated.
Integrate Marine Weather with No-Code API Tools
Connect the Marine Weather API to your favorite automation platform without writing code. Build workflows that leverage marine weather data across thousands of apps.





All platforms use your same API key to access Marine Weather. Visit our integrations hub for step-by-step setup guides.
Frequently Asked Questions
How do I get an API key for Marine Weather?
How many credits does Marine Weather cost?
Each successful Marine Weather API call consumes credits based on plan tier. Check the pricing section above for the exact credit cost. Failed requests and errors don't consume credits, so you only pay for successful marine weather lookups.
Can I use Marine Weather in production?
The free plan is for testing and development only. For production use of Marine Weather, upgrade to a paid plan (Starter, Pro, or Mega) which includes commercial use rights, no attribution requirements, and guaranteed uptime SLAs. All paid plans are production-ready.
Can I use Marine Weather from a browser?
What happens if I exceed my Marine Weather credit limit?
When you reach your monthly credit limit, Marine Weather API requests will return an error until you upgrade your plan or wait for the next billing cycle. You'll receive notifications at 80% and 95% usage to give you time to upgrade if needed.



