Weather API GET

Weather is a simple tool for getting the current weather. It returns the temperature, humidity, and more for a given location.

Try it — live request, no key required

Request

GETapi.apiverve.com/v1/weatherforecast

Verification

Format

No key required to try it. Get a key to use it in your app.

200 OK

{
  "status": "ok",
  "error": null,
  "data": {
    // Weather response payload
  }
}

About the Weather API

What people use it for

Weather App: Use the Weather API to get current weather for a weather app. Use the data to display weather information, provide forecasts, and offer alerts
Travel App: Get current weather by using the Weather API for a travel app. Use the data to plan trips, check conditions, and prepare for travel
Outdoor Activities: Plan outdoor activities by using the Weather API to get current weather. Use the data to schedule events, organize trips, and optimize experiences

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

View all integrations →

Other ways to use Weather

Same data, same APIVerve account, same credit balance — one key works on all of them.

Give it to an AI agentConnect over MCP and your agent calls it as a native tool — Claude, Cursor, ChatGPT.on VerveKit Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.on VerveSheets Ground an agent on itA cited, machine-checkable fact your model can't produce on its own.on VerveContext

Questions.

Common questions about the Weather API.

Read the docs →

What does the Weather API do?

Weather is a simple tool for getting the current weather. It returns the temperature, humidity, and more for a given location.

How do I authenticate Weather API requests?

Pass your API key in the x-api-key header over HTTPS. One key works across all 300+ APIVerve APIs — there are no per-endpoint credentials.

How much does the Weather API cost?

Each call spends 10 credits from your shared pool. The free tier includes 200 credits every month, and paid plans add more headroom.

How fast is the Weather API?

Response time depends on the endpoint — the p50 through p99 latency for this API is published on this page. Requests are served over HTTPS through a global edge network.

What response formats does the Weather API support?

JSON by default, plus XML and YAML via the format parameter. GraphQL and an MCP interface for AI agents are available across the catalog.

What HTTP method does the Weather API use?

GET over HTTPS, following standard REST conventions with a consistent { status, error, data } response envelope.

Request parameters — GET /v1/weatherforecast

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
`city`Required	string	`San Francisco`	The city for which you want to get the current weather (e.g., San Francisco)

Example request

1
2

curl "https://api.apiverve.com/v1/weatherforecast?city=San%20Francisco" \
  -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-key`Required	Every request	Your API key. Header names are case-insensitive, so `X-API-Key` is the same header.
`Authorization`Alternate	Instead of the above	`Bearer <key>` — for clients that only expose bearer auth. Resolves to the same account and the same billing.

401 is the only auth verdict

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/weatherforecast

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.

Sample 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
  }
}

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
`tempC`	number	`13.3`	Current temperature in degrees Celsius
`tempF`	number	`55.9`	Current temperature in degrees Fahrenheit
`windMph`	number	`4.7`	Wind speed in miles per hour
`windKph`	number	`7.6`	Wind speed in kilometers per hour
`windDegree`	number	`273`	Wind direction in degrees (0-360)
`windDir`	string	`"W"`	Wind direction as compass point (N, S, E, W, etc.)
`pressureMb`Premium	number	`1022`	Atmospheric pressure in millibars
`pressureIn`Premium	number	`30.17`	Atmospheric pressure in inches of mercury
`precipMm`Premium	number	`0`	Precipitation amount in millimeters
`precipIn`Premium	number	`0`	Precipitation amount in inches
`feelslikeC`Premium	number	`13`	Apparent temperature in degrees Celsius
`feelslikeF`Premium	number	`55.3`	Apparent temperature in degrees Fahrenheit
`visKm`Premium	number	`16`	Visibility distance in kilometers
`visMiles`Premium	number	`9`	Visibility distance in miles
`gustMph`Premium	number	`7.2`	Wind gust speed in miles per hour
`gustKph`Premium	number	`11.6`	Wind gust speed in kilometers per hour

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 allowance for the cycle
`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	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.

Compare all pricing tiers →

Call it from cURL — GET /v1/weatherforecast

No SDK to install — this is a plain HTTPS call to /v1/weatherforecast with your key in the x-api-key header. Swap in a real key and it runs as-is.

cURL

1
2

curl "https://api.apiverve.com/v1/weatherforecast" \
  -H "x-api-key: YOUR_API_KEY"

Resources

GitHubapiverve/weatherforecast-apiSource, issues and the examples this page is built from.ReferenceWeather API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/weatherforecastnpm APIVerve.API.WeatherNuGet

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/weatherforecast

Install the Node.js SDK, then call the Weather API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — npm

npm install @apiverve/weatherforecast

Node.js

const res = await fetch("https://api.apiverve.com/v1/weatherforecast", {
  headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);

Resources

npm@apiverve/weatherforecastThe published Node.js client, versioned and signed.GitHubapiverve/weatherforecast-apiSource, issues and the examples this page is built from.ReferenceWeather API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

APIVerve.API.WeatherNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Python — GET /v1/weatherforecast

No SDK to install — this is a plain HTTPS call to /v1/weatherforecast with your key in the x-api-key header. Swap in a real key and it runs as-is.

Python

import requests

res = requests.get(
    "https://api.apiverve.com/v1/weatherforecast",
    headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])

Resources

Also published for

@apiverve/weatherforecastnpm APIVerve.API.WeatherNuGet

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/weatherforecast

Install the C# / .NET SDK, then call the Weather API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — NuGet

dotnet add package APIVerve.API.Weather

C# / .NET

using var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");

var json = await client.GetStringAsync("https://api.apiverve.com/v1/weatherforecast");
Console.WriteLine(json);

Resources

NuGetAPIVerve.API.WeatherThe published C# / .NET client, versioned and signed.GitHubapiverve/weatherforecast-apiSource, issues and the examples this page is built from.ReferenceWeather API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/weatherforecastnpm

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Go — GET /v1/weatherforecast

No SDK to install — this is a plain HTTPS call to /v1/weatherforecast 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/weatherforecast", 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

@apiverve/weatherforecastnpm APIVerve.API.WeatherNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from PHP — GET /v1/weatherforecast

No SDK to install — this is a plain HTTPS call to /v1/weatherforecast with your key in the x-api-key header. Swap in a real key and it runs as-is.

PHP

$ch = curl_init("https://api.apiverve.com/v1/weatherforecast");
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

@apiverve/weatherforecastnpm APIVerve.API.WeatherNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Ruby — GET /v1/weatherforecast

No SDK to install — this is a plain HTTPS call to /v1/weatherforecast with your key in the x-api-key header. Swap in a real key and it runs as-is.

Ruby

require "net/http"

uri = URI("https://api.apiverve.com/v1/weatherforecast")
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.body

Resources

Also published for

@apiverve/weatherforecastnpm APIVerve.API.WeatherNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

All articles →

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

Real-Time APIs: WebSockets vs Server-Sent EventsCompare WebSockets and Server-Sent Events for real-time data. Learn when to use each and how to implement them.Read

Weather API GET

Try it — live request, no key required

About the Weather API

What people use it for

Ways to call it

Other ways to use Weather

Questions.

Request parameters — GET /v1/weatherforecast

Required

Authentication

Response — GET /v1/weatherforecast

Response fields

Response headers

Errors

What a call costs — 10 credits per call

Call it from cURL — GET /v1/weatherforecast

Resources

Also published for

Call it from Node.js — GET /v1/weatherforecast

Resources

Also published for

Call it from Python — GET /v1/weatherforecast

Resources

Also published for

Call it from C# / .NET — GET /v1/weatherforecast

Resources

Also published for

Call it from Go — GET /v1/weatherforecast

Resources

Also published for

Call it from PHP — GET /v1/weatherforecast

Resources

Also published for

Call it from Ruby — GET /v1/weatherforecast

Resources

Also published for

Zero-code embed — one snippet, no backend

Changelog — Weather API

Weather

Related articles

Ready to build with Weather? Start with 200 free credits — one key unlocks all 300+ APIs.

Explore the catalog