Skip to content
Free API Today

US National Weather Service API

Forecast office, grid and forecast links for a point in the United States.
Status
Working
API key
Not needed
Browser calls
Runs in the browser
Latency
206 ms
Docs
www.weather.gov ↗

Build snapshot, not live. One verifier run on , from the machine that built this site. How we check

Example request

GEThttps://api.weather.gov/points/39.7456,-97.0892

Sent from your browser straight to api.weather.gov. No proxy: this site never sees the request or the answer.

Copy the request

Shell
curl -s 'https://api.weather.gov/points/39.7456,-97.0892'

Response stored by the verifier

This is what api.weather.gov answered when the verifier sent the request above on : HTTP 200, application/geo+json. Arrays are cut to two items and long strings are shortened. It comes from the build snapshot.

application/geo+json · stored
{
  "@context": [
    "https://geojson.org/geojson-ld/geojson-context.jsonld",
    {
      "@version": "1.1",
      "wx": "https://api.weather.gov/ontology#",
      "s": "https://schema.org/",
      "geo": "http://www.opengis.net/ont/geosparql#",
      "unit": "http://codes.wmo.int/common/unit/",
      "@vocab": "https://api.weather.gov/ontology#",
      "geometry": {
        "@id": "s:GeoCoordinates",
        "@type": "geo:wktLiteral"
      },
      "city": "s:addressLocality",
      "state": "s:addressRegion",
      "distance": {
        "@id": "s:Distance",
        "@type": "s:QuantitativeValue"
      },
      "bearing": {
        "@type": "s:QuantitativeValue"
      },
      "value": {
        "@id": "s:value"
      },
      "unitCode": {
        "@id": "s:unitCode",
        "@type": "@id"
      },
      "forecastOffice": {
        "@type": "@id"
      }
    }
  ],
  "id": "https://api.weather.gov/points/39.7456,-97.0892",
  "type": "Feature",
  "geometry": {
    "type": "Point",
    "coordinates": [
      -97.0892,
      39.7456
    ]
  },
  "properties": {
    "@id": "https://api.weather.gov/points/39.7456,-97.0892",
    "@type": "wx:Point",
    "cwa": "TOP",
    "type": "lan
…

Availability

Up 1 of 1 day checked · 30-day window

What counts as up for this API: an answer within five seconds, a 2xx status, and the JSON body must contain the field "properties".

Last check: — passed, HTTP 200 in 206 ms.

The check runs from our infrastructure, not from where you are. If you need certainty, send the request yourself above. How the verifier works.

Questions

Does the US National Weather Service API need an API key?

No. The sample request on this page was answered without a key, token or account. Note: US coverage only. Asks every client to send a descriptive User-Agent. Browsers send their own; set one in server code.

Can I call the US National Weather Service API from the browser?

Yes. api.weather.gov answered our verifier with an Access-Control-Allow-Origin header on Oct 3, 2026, so a fetch call from a web page can read the response.

Is the US National Weather Service API working?

At the check on Oct 3, 2026 it returned HTTP 200 with the expected data in 206 ms. The status at the top of this page shows the most recent result we have.