Reference · built on requestCommons signalAviation & marine

FAA NOTAM API

Notices to Air Missions from the FAA's Federal NOTAM System through a REST API on the FAA API Portal, with approved client credentials.

Request accessPricing ↗

About

The FAA publishes Notices to Air Missions through the Federal NOTAM System (FNS). Its NOTAM API is a request and response REST service described in the OpenAPI standard, listed on the FAA API Portal at api.faa.gov, and fed from FNS NOTAM Distribution Service data on SWIM. The FAA's NOTAM team states the API returns NOTAMs as GeoJSON, includes all NOTAMs, and carries the same TFR geometry as tfr.faa.gov. Access follows the portal's process: register, request access to the API for a named application, wait for review, then read client_id and client_secret under My Applications.

Through Fibric, an operator watches NOTAMs for the airports and airspace your operation depends on and proposes a hold, a re-route, or a permit check for your approval.

This is a reference listing. It documents what Fibric would read from FAA NOTAM API and what it could propose, based on the publisher's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • NOTAMs published through the Federal NOTAM System, read by request and response over REST; the FAA describes the API in the OpenAPI standard
  • NOTAMs as GeoJSON, which the FAA's NOTAM team states the API presents
  • All NOTAMs, domestic and international, since the API depends on FNS NDS from SWIM as its source
  • TFR NOTAMs with geometry the FAA states is the same as tfr.faa.gov
  • ICAO-format NOTAMs as FNS moves to publish all NOTAMs in ICAO format under Order 7930.2
  • Endpoints, request and response payloads, and a RAML or OAS download of the specification on the API's portal page after login

Proposed actions

Read-only. This feed informs operators; it changes nothing.

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Hold a drone job when a NOTAM closes the airspace

    The operator reads NOTAMs and TFR geometry for the job site before dispatch and proposes a hold on the work order when a restriction covers it.

    With Permit Check

  • Flag inbound freight through a closed runway

    When a NOTAM closes a runway or airport your carrier uses, the operator proposes a delay flag on open inbound shipments routed through it.

    With Inbound Delay

  • Put airspace restrictions in the morning brief

    The operator lists new NOTAMs for the airports you operate from and adds them to the brief with the NOTAM text attached.

    With Morning Brief

Requirements

  • An FAA API Portal account; external users sign in with a registered user id and password, FAA staff with FAA SSO
  • An access request for the NOTAM API naming your application and the Production instance, which the FAA reviews and confirms by email
  • client_id and client_secret from My Applications, sent as request headers on every call
Authentication
client_id and client_secret request headers, issued through the FAA API Portal after you register, request access for a named application, and the FAA approves it.

Limits

  • The portal and the API's specification sit behind a MyAccess login; the FAA's public pages list no parameters or rate limits
  • Access waits on FAA review and approval of your request before credentials appear under My Applications
  • The endpoint at external-api.faa.gov/notamapi/v1/notams answers 401 Unauthorized without the credential headers
  • During a NOTAM system outage, candidate NOTAMs go out through notambackup.faa.gov, outside the NOTAM system, and carry no NOTAM numbers

Access and pricing

Reference listing. Public feed access is separate from Fibric integration. If you request this feed, your quote covers the build, usage, and support.

Request FAA NOTAM API ↗

Questions and answers

How do you get credentials for the FAA NOTAM API?
Register on the FAA API Portal at api.faa.gov, find the API under APIs, click Request Access, name your application, and pick the Production instance. After review, the FAA emails you; credentials then appear under My Applications, and you send client_id and client_secret as request headers.
What format does the API return?
The FAA's NOTAM team answered that the API presents NOTAMs as GeoJSON. The FAA describes the service as a pure request and response REST API in the OpenAPI standard; the full specification downloads from the portal in RAML or OAS after login.
Is there a push feed instead of polling?
Not from this API. The FAA lists the FNS NOTAM Publication Service, which publishes NOTAMs by JMS over SWIM through the SWIM Cloud Distribution Service, as the feed option. The NOTAM API is request and response only.
Ask about FAA NOTAM API

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This Commons signal listing is developed, published, and supported by Fibric. It reads public data published by Federal Aviation Administration, FAA API Portal (api.faa.gov; endpoint host external-api.faa.gov). Upstream agencies and projects are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy