Docs/APIs/Weather

Weather

Get Current Weather

OperationalCredits 10 per callp50 905msWeatherStar

Overview

Query either a city name or a zip code to fetch real-time atmospheric readings. Responses supply temperature, wind speed, and compass heading in both metric and imperial measurements. Paid plans add precipitation amounts, barometric pressure, apparent feels-like temperatures, visibility, and wind gust speeds.

Endpoint

One host, one path per API. The block below shows this call in four languages; every one of them is the same HTTP request. Making requests covers the timeouts, retries and parameter rules that apply to all of them. The SDKs wrap the same call in a typed client.

GEThttps://api.apiverve.com/v1/weatherforecast
curl "https://api.apiverve.com/v1/weatherforecast?city=San%20Francisco" \
  -H "x-api-key: your_api_key_here"

Replace your_api_key_here with the key from your dashboard. When the inputs arrive as a list rather than one at a time, batch requests run up to 200 of them through this same API in a single call.

Authentication

Send your key in the x-api-key header. That is the only auth step — there is no token exchange and no per-endpoint scope to configure. Authentication covers creating, rotating and revoking keys.

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.

Parameters

Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them.

ParameterTypeDescription
cityRequiredstringThe city for which you want to get the current weather (e.g., San Francisco)

Response

Every API returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape. Response format covers the envelope, the other output formats and how premium fields are withheld.

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.

FieldTypeExampleDescription
tempCnumber13.3Current temperature in degrees Celsius
tempFnumber55.9Current temperature in degrees Fahrenheit
windMphnumber4.7Wind speed in miles per hour
windKphnumber7.6Wind speed in kilometers per hour
windDegreenumber273Wind direction in degrees (0-360)
windDirstring"W"Wind direction as compass point (N, S, E, W, etc.)
pressureMbPremiumnumber1022Atmospheric pressure in millibars
pressureInPremiumnumber30.17Atmospheric pressure in inches of mercury
precipMmPremiumnumber0Precipitation amount in millimeters
precipInPremiumnumber0Precipitation amount in inches
feelslikeCPremiumnumber13Apparent temperature in degrees Celsius
feelslikeFPremiumnumber55.3Apparent temperature in degrees Fahrenheit
visKmPremiumnumber16Visibility distance in kilometers
visMilesPremiumnumber9Visibility distance in miles
gustMphPremiumnumber7.2Wind gust speed in miles per hour
gustKphPremiumnumber11.6Wind gust speed in kilometers per hour

Errors

Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change. Error handling covers the full status list and which of them are worth retrying.

StatusMeaningWhat to do
400Input was rejectedRead error; it names the parameter.
401Key missing or invalidCheck the header name and the key value.
403Key valid, but not permittedA key restriction or IP allow-list; see key scoping.
429Rate limited, or out of creditsRead error to tell them apart; see rate limits.

Start from a template

A working app built on this API, ready to deploy with your own key. Vercel asks for the key when you deploy; the code is on GitHub to change first.

Use cases

Delivery Route Planning
When high winds threaten courier safety, dispatch software checks live wind speeds and compass direction across delivery zones before assigning routes.
Travel Booking Portals
Travel sites display real-time temperatures for destination cities so travelers know what conditions to expect upon arrival.
Smart Home Thermostats
Home automation platforms read outdoor temperatures for local zip codes to adjust heating and cooling cycles throughout the day.
Outdoor Event Management
Organizers monitor current wind speeds and temperatures by city to decide when to secure temporary staging or postpone outdoor activities.

Other ways to use Weather

Set up Weather on APIVerve, or reach the same source a different way. Your APIVerve account and credits work on all of them — one key, one balance.

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

Pages that use this API:

More in Weather:

Was this page helpful?