A no-key weather API for tutorials and tests: current conditions, daily and hourly forecasts in US or metric units, state alerts, and outage, timeout and stale-data scenarios. Values are synthetic and deterministic, never real observations.
Base URL: https://funapi.dev/api/weather/v1 · 5 endpoints · OpenAPI 3.1 spec and Postman collection available. New here? Read the getting started guide.
supported places
GET /weather/v1/locations — Supported locations with coordinates and time zones · Responds with 200 Link to this endpointcurrent and forecast
GET /weather/v1/current — Current conditions (deterministic per location and hour) · Responds with 200 400 404 503 504 Link to this endpointGET /weather/v1/forecast — Daily forecast, 1–7 days · Responds with 200 400 404 503 504 Link to this endpointGET /weather/v1/hourly — Hourly temperatures, 1–48 hours · Responds with 200 400 404 Link to this endpointstate alerts
GET /weather/v1/alerts — Active alerts for a US state (may be an empty list) · Responds with 200 400 Link to this endpointThe Weather API answers the most common tutorial request — "a free weather API with no key" — with data that is deterministic instead of live, so the same request gives the same forecast all day and a test can assert on it. It returns °F and mph by default or °C and km/h with units=si, and its scenario parameter turns on a 503 outage with Retry-After, a slow 504 or a stale response with a Warning header.
GET https://funapi.dev/api/weather/v1/locations — Supported locations with coordinates and time zones. No token, no signup:
curl -i https://funapi.dev/api/weather/v1/locations
Response: 200 OK
{
"data": [
{
"id": "new-york",
"name": "New York, NY",
"latitude": 40.71,
"longitude": -74.01,
"timeZone": "America/New_York"
},
{
"id": "los-angeles",
"name": "Los Angeles, CA",
"latitude": 34.05,
"longitude": -118.24,
"timeZone": "America/Los_Angeles"
},
{
"id": "chicago",
"name": "Chicago, IL",
"latitude": 41.88,
"longitude": -87.63,
"timeZone": "America/Chicago"
},
{
"id": "austin",
"name": "Austin, TX",
"latitude": 30.27,
"longitude": -97.74,
"timeZone": "America/Chicago"
},
{
"id": "denver",
"name": "Denver, CO",
"latitude": 39.74,
"longitude": -104.99,
"timeZone": "America/Denver"
},
{
"id": "seattle",
"name": "Seattle, WA",
"latitude": 47.61,
"longitude": -122.33,
"timeZone": "America/Los_Angeles"
},
{
"id": "miami",
"name": "Miami, FL",
"latitude": 25.76,
"longitude": -80.19,
"timeZone": "America/New_York"
},
(truncated — the full response comes back when you run it)
How this differs from the National Weather Service API
Last updated