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

Skymerse Notams API

The Notams API from Skymerse — 9 operation(s) for notams.

Skymerse Notams API is published by Skymerse on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include NOTAMs. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 9 operations across 9 paths, and defines 34 schemas. It is described by OpenAPI 3.2.0, at version 0.0.11.

Requests are made against a single base URL, https://api.notamify.com/api/v2.

9 operations 9 paths 34 schemas 7 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.0.11
Base URL
https://api.notamify.com/api/v2
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Skymerse Notams API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

Paths & Operations 9

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

Notams 9
GET
/notams/recently-expired
Get recently expired NOTAMs
6 params → 200
GET
/notams/archive
9 params → 200404
GET
/notams
12 params → 200
GET
/notams/nearby
14 params → 200
POST
/notams/prioritisation
Prioritise a NOTAM with AI
body → 200
GET
/notams/raw
Get active NOTAMs without interpretations
12 params → 200
POST
/notams/briefing
Generate flight briefing
body → 201400
GET
/notams/briefing/simple
Generate simple airport briefing
4 params → 200404
GET
/notams/briefing/{uuid}
Get briefing job status
1 param → 200202404500

Schemas 34

The contract defines 34 schemas that model the data the API accepts and returns. The most detailed are AircraftDetails (17 properties), RecentlyExpiredNotamDTO (16 properties), NotamDTO (14 properties), NotamInterpretationDTO (8 properties). Each schema is shown below with its type and property counts.

ValueDTO
object
3 properties 1 required
NotamPrioritisationRequest
object
Flight profile request extended with the NOTAM identifier to evaluate.
7 properties 2 required
LocationType
string
Types of locations in a flight plan.
AffectedElementClauseDTO
object
6 properties 3 required
ProcedureCapabilityDTO
object
5 properties 1 required
NotamListResult
object
4 properties 4 required
GenerateFlightBriefingResponse
object
2 properties 2 required
RecentlyExpiredNotamListResult
object
4 properties 4 required
NotamMapElementDTO
object
Data Transfer Object for NOTAM map elements.
8 properties 3 required
SimpleAirportBriefingResponse
object
3 properties 2 required
NotamInterpretationDTO
object
8 properties 4 required
GroupedMeasurementValueDTO
object
3 properties 1 required
NotamDTO
object
Data Transfer Object (DTO) for a NOTAM (Notice to Air Missions). Attributes: notamnumber (str): The unique identifier for the NOTAM location (str): The facilit…
14 properties 9 required
AffectedElementChangeDTO
object
5 properties 1 required
FractionalMeasurementValueDTO
object
5 properties 4 required
AffectedElementDTO
object
6 properties 3 required
BriefingJobStatusDTO
object
DTO returned by the status endpoint for a briefing job.
5 properties 4 required
NotamScheduleInterpretationDTO
object
5 properties 3 required
RecentlyExpiredNotamDTO
object
DTO for recently expired NOTAM responses. This intentionally extends only the new recently expired endpoint's response shape so existing v2 NotamDTO-based endp…
16 properties 9 required
CriticalOperationalRestrictionGroup
object
3 properties 1 required
NotamPriority
string
Priority levels returned by the prioritisation model.
NotamPrioritisationResult
object
Envelope returned by the API endpoint.
4 properties 4 required
ScalarMeasurementValueDTO
object
4 properties 3 required
AffectedElementSemanticsDTO
object
4 properties
PrioritizedNotamDTO
object
API representation combining original NOTAM data with GPT assessment.
4 properties 3 required
MeasurementComponentValueDTO
object
3 properties 3 required
ValueComponentDTO
object
3 properties 1 required
AircraftDetails
object
17 properties
GenerateFlightBriefingRequest
object
6 properties 1 required
AircraftDesignatorValueDTO
object
3 properties 3 required
BriefingResponse
object
2 properties 1 required
AffectedElementReferenceDTO
object
5 properties 1 required
LocationWithType
object
Location (airport or FIR) with optional type and time window.
6 properties 3 required
BriefingStatus
string
Status of a briefing job.

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

skymerse-notams-api-openapi.yml Raw ↑
Where this information came from

This is an independent, third-party profile of Skymerse Notams 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.