How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
NOAA

NOAA Stations API

The Stations API from NOAA — 7 operation(s) for stations.

Documentation Provider Profile APIs.io OpenAPI GitHub

NOAA Stations API is one of 17 APIs that NOAA publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 9 JSON Schema definitions.

Tagged areas include Stations. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a GitHub repository, and 9 JSON Schemas.

This API exposes 7 operations across 7 paths, and defines 30 schemas. It is described by OpenAPI 3.2.0, at version v4.0.

Requests are made against a single base URL, https://api.weather.gov.

7 operations 7 paths 30 schemas 7 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v4.0
Base URL
https://api.weather.gov
Terms of Service
View terms
Resource Areas
1

Paths & Operations 7

Across 7 paths, the API surfaces 7 operations — 7 GET. Each is listed below with its method, path, parameters, and response codes.

Stations 7
GET
/stations/{stationId}/observations
Returns a list of observations for a given station
station_observation_list 5 params → 200default
GET
/stations/{stationId}/observations/latest
Returns the latest observation for a station
station_observation_latest 2 params → 200default
GET
/stations/{stationId}/observations/{time}
Returns a single observation.
station_observation_time 2 params → 200default
GET
/stations/{stationId}/tafs
Returns Terminal Aerodrome Forecasts for the specified airport station.
tafs 1 param → 200default
GET
/stations/{stationId}/tafs/{date}/{time}
Returns a single Terminal Aerodrome Forecast.
taf 3 params → 200default
GET
/stations
Returns a list of observation stations.
obs_stations 4 params → 200default
GET
/stations/{stationId}
Returns metadata about a given observation station
obs_station 1 param → 200default

Schemas 30

The contract defines 30 schemas that model the data the API accepts and returns. The most detailed are Observation (30 properties), ObservationStation (15 properties), ProblemDetail (6 properties), QuantitativeValue (5 properties). Each schema is shown below with its type and property counts.

GeoJsonGeometry
A GeoJSON geometry object. Please refer to IETF RFC 7946 for information on the GeoJSON format.
Date
string
Date (in YYYY-MM-DD format).
Observation
object
30 properties
ObservationCollectionGeoJson
MetarPhenomenon
object
An object representing a decoded METAR phenomenon string.
5 properties 4 required
AreaCode
State/territory codes and marine area codes
StateTerritoryCode
string
ObservationJsonLd
MarineAreaCode
string
Marine area code as defined in NWS Directive 10-302: AM: Western North Atlantic Ocean and along U.S. East Coast south of Currituck Beach Light NC following the…
GeometryString
stringnull
A geometry represented in Well-Known Text (WKT) format.
ObservationCollectionJsonLd
object
3 properties
Time
string
A time (in HHMM format). This is always specified in UTC (Zulu) time.
JsonLdContext
GeoJsonCoordinate
array
A GeoJSON coordinate. Please refer to IETF RFC 7946 for information on the GeoJSON format.
ObservationStation
object
15 properties
ObservationGeoJson
GeoJsonBoundingBox
array
A GeoJSON bounding box. Please refer to IETF RFC 7946 for information on the GeoJSON format.
GeoJsonFeatureCollection
object
A GeoJSON feature collection. Please refer to IETF RFC 7946 for information on the GeoJSON format.
3 properties 2 required
MetarSkyCoverage
string
ObservationStationCollectionGeoJson
ObservationStationCollectionJsonLd
object
4 properties
ProblemDetail
object
Detail about an error. This document conforms to RFC 7807 (Problem Details for HTTP APIs).
6 properties 6 required
UnitOfMeasure
string
A string denoting a unit of measure, expressed in the format "{unit}" or "{namespace}:{unit}". Units with the namespace "wmo" or "wmoUnit" are defined in the W…
GeoJsonFeature
object
A GeoJSON feature. Please refer to IETF RFC 7946 for information on the GeoJSON format.
5 properties 3 required
GeoJsonPolygon
array
A GeoJSON polygon. Please refer to IETF RFC 7946 for information on the GeoJSON format.
ObservationStationGeoJson
PaginationInfo
object
Links for retrieving more data from paged data sets
1 property 1 required
QuantitativeValue
object
A structured value representing a measurement and its unit of measure. This object is a slightly modified version of the schema.org definition at https://schem…
5 properties
GeoJsonLineString
array
A GeoJSON line string. Please refer to IETF RFC 7946 for information on the GeoJSON format.
ObservationStationJsonLd

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

noaa-stations-api-openapi.yml Raw ↑

Other APIs NOAA publishes across the network.

Climate Data Online (CDO) API
AE Profile APIs.io
CO-OPS Tides and Currents API
AE Profile APIs.io
NOAA Alerts API
AE Profile APIs.io
NOAA Aviation API
AE Profile APIs.io
NOAA Glossary API
AE Profile APIs.io
NOAA Gridpoints API
AE Profile APIs.io
NOAA Icons API
AE Profile APIs.io
NOAA Navigational Data API
AE Profile APIs.io
NOAA Offices API
AE Profile APIs.io
NOAA Points API
AE Profile APIs.io
NOAA Products API
AE Profile APIs.io
NOAA Radar API
AE Profile APIs.io
#Stations
← Back to N APIs
API Details
ID
noaa:noaa-stations-api
Base URL
https://api.weather.gov
Docs
https://www.weather.gov/documentation/services-web-api
Provider
NOAA
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=noaa-stations-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/noaa-stations-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of NOAA Stations API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.