Async briefings endpoint (get-briefing v2)

The Flight Briefing API provides an asynchronous endpoint for generating flight-focused NOTAM briefings with intelligent chip-based output formatting. The API supports both structured flight briefings (with origin/destination/alternate roles) and flexible location-based briefings. The endpoint provides briefing with Briefings chips system to clearly indicate which notams are relevant for the flight.

Endpoint Structure

The briefing API uses an asynchronous pattern requiring two steps:

  1. POST /api/v2/notams/briefing - Submit briefing request

  2. GET /api/v2/notams/briefing/{uuid} - Pull for results

Request Body

The API supports two briefing formats:

Structured Flight Briefing

Traditional flight briefing with specific roles for each location:

{
  "locations": [
    {
      "location": "EPWA",
      "type": "origin",
      "starts_at": "2025-08-11T10:00:00Z",
      "ends_at": "2025-08-11T16:00:00Z"
    },
    {
      "location": "EGLL",
      "type": "destination",
      "starts_at": "2025-08-11T11:30:00Z",
      "ends_at": "2025-08-11T18:00:00Z"
    },
    {
      "location": "EPRZ",
      "type": "alternate",
      "starts_at": "2025-08-11T10:00:00Z",
      "ends_at": "2025-08-11T20:00:00Z"
    }
  ],
  "origin_runway": "RWY11",
  "destination_runway": "RWY27L",
  "destination_procedure": "ILS27L",
  "aircraft_type": "B738"
}

Flexible Location Briefing

Flexible briefing without structured location roles:

Generate flight briefing

post

Generate a flight-focused NOTAM briefing asynchronously. Supports both structured flight briefings (with origin/destination/alternate types) and flexible location-based briefings.

Authorizations
AuthorizationstringRequired
Bearer authentication header of the form Bearer <token>.
Body
origin_runwayany ofOptional

The planned origin airport runway (e.g. 33)

string · min: 1 · max: 7Optional
or
nullOptional
destination_runwayany ofOptional

The planned destination airport runway (e.g. 18R)

string · min: 1 · max: 7Optional
or
nullOptional
destination_procedureany ofOptional

The planned destination airport landing procedure (e.g. ILS18R etc.)

string · min: 1 · max: 15Optional
or
nullOptional
aircraft_typeany ofOptional

The type of aircraft (e.g. A320, B737, etc.)

string · min: 1 · max: 15Optional
or
nullOptional
aircraft_detailsany ofOptional

The details of the aircraft

or
nullOptional
Responses
post
/notams/briefing

Get briefing job status

get

Get the status and result of a briefing job by UUID

Authorizations
AuthorizationstringRequired
Bearer authentication header of the form Bearer <token>.
Path parameters
uuidstringRequired

The UUID of the briefing job

Responses
200

Briefing completed successfully

application/json
get
/notams/briefing/{uuid}

Best Practices

Polling Strategy

  1. Initial Delay: Wait 2-3 seconds before first poll

  2. Maximum Polls: Limit to 120 polls (approximately 4 minutes)

  3. Error Handling: Implement retry logic for network failures

Example Polling Implementation

Last updated