Weather API
Overview
To use 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/weatherforecastExample
How to call the Weather API in different programming languages.
curl -X GET \
"https://api.apiverve.com/v1/weatherforecast?city=San%20Francisco" \
-H "X-API-Key: your_api_key_here"const response = await fetch('https://api.apiverve.com/v1/weatherforecast?city=San%20Francisco', {
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/weatherforecast?city=San%20Francisco', headers=headers)
data = response.json()
print(data)package main
import (
"fmt"
"io"
"net/http"
)
func main() {
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/weatherforecast?city=San%20Francisco", 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))
}{
"status": "ok",
"error": null,
"data": {
"tempC": 13.3,
"tempF": 55.9,
"windMph": 4.7,
"windKph": 7.6,
"windDegree": 273,
"windDir": "W",
"pressureMb": 1022,
"pressureIn": 30.17,
"precipMm": 0,
"precipIn": 0,
"feelslikeC": 13,
"feelslikeF": 55.3,
"visKm": 16,
"visMiles": 9,
"gustMph": 7.2,
"gustKph": 11.6
}
}Authentication
The 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 Weather API directly in your browser with live requests and responses.
Parameters
The Weather API supports multiple query options. Use one of the following:
Option 1: Get Current Weather by City
| Parameter | Type | Required | Description | Default | Example |
|---|---|---|---|---|---|
city | string | required | The city for which you want to get the current weather (e.g., San Francisco) | - |
Option 2: Get Current Weather by Zip Code
| Parameter | Type | Required | Description | Default | Example |
|---|---|---|---|---|---|
zip | string | required | The zip code for which you want to get the current weather | - |
Response
The Weather API returns responses in JSON, XML, YAML, and CSV formats. The JSON response is shown in the Example section above; alternative formats below.
Other Response Formats
<?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>
<tempC>13.3</tempC>
<tempF>55.9</tempF>
<windMph>4.7</windMph>
<windKph>7.6</windKph>
<windDegree>273</windDegree>
<windDir>W</windDir>
<pressureMb>1022</pressureMb>
<pressureIn>30.17</pressureIn>
<precipMm>0</precipMm>
<precipIn>0</precipIn>
<feelslikeC>13</feelslikeC>
<feelslikeF>55.3</feelslikeF>
<visKm>16</visKm>
<visMiles>9</visMiles>
<gustMph>7.2</gustMph>
<gustKph>11.6</gustKph>
</data>
</response>
status: ok
error: null
data:
tempC: 13.3
tempF: 55.9
windMph: 4.7
windKph: 7.6
windDegree: 273
windDir: W
pressureMb: 1022
pressureIn: 30.17
precipMm: 0
precipIn: 0
feelslikeC: 13
feelslikeF: 55.3
visKm: 16
visMiles: 9
gustMph: 7.2
gustKph: 11.6
| key | value |
|---|---|
| tempC | 13.3 |
| tempF | 55.9 |
| windMph | 4.7 |
| windKph | 7.6 |
| windDegree | 273 |
| windDir | W |
| pressureMb | 1022 |
| pressureIn | 30.17 |
| precipMm | 0 |
| precipIn | 0 |
| feelslikeC | 13 |
| feelslikeF | 55.3 |
| visKm | 16 |
| visMiles | 9 |
| gustMph | 7.2 |
| gustKph | 11.6 |
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 |
|---|---|---|---|
tempC | number | Current temperature in degrees Celsius | |
tempF | number | Current temperature in degrees Fahrenheit | |
windMph | number | Wind speed in miles per hour | |
windKph | number | Wind speed in kilometers per hour | |
windDegree | number | Wind direction in degrees (0-360) | |
windDir | string | Wind direction as compass point (N, S, E, W, etc.) | |
pressureMbPremium | number | Atmospheric pressure in millibars | |
pressureInPremium | number | Atmospheric pressure in inches of mercury | |
precipMmPremium | number | Precipitation amount in millimeters | |
precipInPremium | number | Precipitation amount in inches | |
feelslikeCPremium | number | Apparent temperature in degrees Celsius | |
feelslikeFPremium | number | Apparent temperature in degrees Fahrenheit | |
visKmPremium | number | Visibility distance in kilometers | |
visMilesPremium | number | Visibility distance in miles | |
gustMphPremium | number | Wind gust speed in miles per hour | |
gustKphPremium | number | Wind gust speed in kilometers per hour |
Headers
Only X-API-Key is required. Optional headers include Accept for response format negotiation (JSON, XML, or YAML), User-Agent, and X-Request-ID for request tracing. See all request headers →
GraphQL AccessALPHA
Access Weather through GraphQL to combine it with other API calls in a single request. Query only the 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 {
weatherforecast(
input: {
city: "San Francisco"
}
) {
tempC
tempF
windMph
windKph
windDegree
windDir
pressureMb
pressureIn
precipMm
precipIn
feelslikeC
feelslikeF
visKm
visMiles
gustMph
gustKph
}
}Note: Authentication is handled via the x-api-key header in your GraphQL request, not as a query parameter.
CORS Support
The Weather API accepts cross-origin requests from any origin, so it can be called directly from browser-based applications without a proxy. See CORS support →
Rate Limiting
Weather requests are throttled per minute on the Free plan and unthrottled on paid plans. Exceeding the limit returns 429 Too Many Requests; rate-limit usage is reported in the X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset response headers. See per-plan limits and best practices →
Error Codes
The Weather API uses standard HTTP status codes — 200 on success, 400 for invalid parameters, 401 for missing or invalid keys, 403 for insufficient credits, 429 for rate-limit exhaustion, and 500/503 for server-side issues. Each error response includes an X-Request-ID header you can quote when contacting support. See full error handling guide →
SDKs for Weather
Official Weather packages on npm, PyPI, NuGet, and JitPack — plus a Postman collection and an OpenAPI spec. See the SDK guide →
No-Code Integrations
Weather works with Zapier, Make, Pipedream, n8n, and Power Automate using the same API key. See setup guides →
Frequently Asked Questions
How do I get an API key for Weather?
How many credits does Weather cost?
Each successful 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 weather lookups.
Can I use Weather in production?
The free plan is for testing and development only. For production use of 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 Weather from a browser?
What happens if I exceed my Weather credit limit?
When you reach your monthly credit limit, 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.








