Submit flight plans
POST/flight-plans/v5/
Submit flight plans to SkyPath system. This will enable SkyPath system to present the most accurate flight plans for your pilots and dispatchers. This endpoint also supports updating previously created flight plans. It can unlock automated desk integration for dispatchers using SkyPath web app.
To update an existing flight plan, submit a POST request with the same values for all the following fields:
callsign
depAirportIcao
arrAirportIcao
scheduledArrival
These fields are used together to uniquely identify the flight plan in the SkyPath system.
If a match is found, the existing plan will be updated. If not, a new flight plan will be created.
The callsign
is normalized internally (leading zeros in the numeric part are removed), so ensure consistency in formatting when updating.
Partial updates are supported — only fields included in the request will be updated.
Staging Url: https://staging-api.skypath.io/flight-plans/v5/
Request
- application/json
Body
required
Array [
]
Possible values: non-empty
and <= 20 characters
The callsign of the flight. Example: XXX0001
Possible values: <= 9999
The flight number
Possible values: non-empty
and <= 6 characters
The flight number in IATA format
Possible values: non-empty
and <= 7 characters
The flight number in ICAO format
Possible values: non-empty
and <= 20 characters
The aircraft registration number
Possible values: non-empty
and <= 10 characters
The aircraft ICAO code
Possible values: non-empty
and <= 10 characters
The aircraft IATA code
Possible values: non-empty
and <= 2 characters
The airline IATA code
Possible values: non-empty
and <= 3 characters
The airline ICAO code
Possible values: non-empty
and <= 4 characters
The departure airport ICAO code
Possible values: non-empty
and <= 3 characters
The departure airport IATA code
Possible values: non-empty
and <= 4 characters
The arrival airport ICAO code
Possible values: non-empty
and <= 3 characters
The arrival airport IATA code
Possible values: non-empty
and <= 10 characters
The desk ID
waypoints
object[]
required
Possible values: >= -90
and <= 90
Latitude of the waypoint in decimal degrees (-90 to 90)
Possible values: >= -180
and <= 180
Longitude of the waypoint in decimal degrees (-180 to 180)
Possible values: <= 520
Responses
- 200
- 401
Flight plan created successfully
- application/json
- Schema
- Example (from schema)
Schema
data
object
meta
object
links
object
warnings
object
{
"data": {
"message": "Flight plan created"
},
"meta": {},
"links": {},
"warnings": {}
}
Unauthorized
- application/json
- Schema
- Example (from schema)
Schema
data
object
meta
object
links
object
warnings
object
{
"data": {
"statusCode": 401,
"code": "401001",
"error": "Unauthorized",
"message": "The method requires authentication but it was not presented or is invalid."
},
"meta": {},
"links": {},
"warnings": {}
}