Loading spreadsheet…
Opening in Numbers for Mac...
Your browser isn’t fully supported.
For the best Numbers for iCloud experience, use a supported browser.
Learn More
Cancel
Continue
Card Name
Card Description
List Name
Labels
et Flight Plan - Sending 0.0 lat/lng instead of null (see description
**0 is something. Null is nothing.** A null coordinate should be the proper way to tell if the API server had found
**nothing**. A zero coordinate can be interpreted as valid (such as latitudes along the equator).
Issues
Live API (blue)
Docs doesn't appropriately mention ALL nullable values (see des
It would also be better to mention if they can be null in the "Type" column and in the "Description" if there's any
additional info. This makes the API somewhat unpredictable. For example in the v2/sessions/{sessionId}/flights endpoint
the username can be null (not empty string) if the user is anonymous. Then it is reasonable to assume that v2/sessions/
{sessionId}/atc will also send back a null for the username (if needs be). But that is not the case. The API can send a
non-empty string with a "fake" username for presentation ("Controller"). Complete list of what I could get : v2/users :
UserStats - discourseUsername UserStats - virtualOrganization v2/sessions/{sessionId}/atc : ActiveATCFacility -
username ActiveATCFacility - virtualOrganization ActiveATCFacility - airportName v2/users/{userId}/atc/{atcSessionId} :
ATCFacility - airportIcao v2/sessions/{sessionId}/flights : FlightEntry - virtualOrganization FlightEntry - username v2/
sessions/{sessionId}/flights/{flightId}/flightplan : FlightPlanItem - name FlightPlanItem - children FlightPlanItem - identifi er
v2/tracks : OceanicTrack - eastLevels OceanicTrack - westLevels v2/users/{userId}/flights & v2/users/{userId}/atc :
PaginatedList - data v2/users/{userId}/flights & v2/users/{userId}/flights/{flightId} : UserFlight - liveryId (mentioned in
another issue) UserFlight - callsign v2/sessions/{sessionId}/notams : NotamResult - sessionId
Issues
Live API (blue)
Get User Flights - add violations received during flight
Feature Requests
Live API (blue)
Kafka Topic or any producer for IF events
https://community.infi niteflight.com/t/request-suggestion-a-kafka-topic-or-a-subscribable-stream-for-if-events/675603
Feature Requests
Live API (blue)
me fi eld (completely distinct from airportIcao) with the full name in
Feature Requests
Live API (blue)
Include a user's roles in the flights endpoint
Feature Requests
Live API (blue)
Search userIds with username regex expression
Feature Requests
Live API (blue)
Get a list of userIds by role
Get a list of userIds of specifi c groups such as IFATCs / mods / staff / other....
Feature Requests
Live API (blue)
Get Flights - Active / Away status
Feature Requests
Live API (blue)
HTTP POST) - Number of online ATC sessions (we have onlineFl
Feature Requests
Live API (blue)
Get User ATC Session(s) - Number of violations issued
Feature Requests
Live API (blue)
Get User ATC Session(s) - Server name
Feature Requests
Live API (blue)
een updates. Helps to perfectly sync with IF (example useful case
Feature Requests
Live API (blue)
ail - Fetch grade/other requirements (Get Sessions returns only if
Feature Requests
Live API (blue)
Get User Detail / Post User Stats - Number of online ATC sessions
Feature Requests
Live API (blue)
Get User Detail / Post User Stats - Total time ATC Sessions
Feature Requests
Live API (blue)
Get ATC Schedule
Feature Requests
Live API (blue)
s/{userId}/flights returning systematically null values for the liveryI
It seems that the liveryId returns a correct value for some people such as KaiM & Laura but for most people it seems
that it doesn't.
Done
Live API (blue)
ATC Actions for non-IFATC and Time Periods
In Live API UserDetails endpoint. Request by Chris_S via IFC. See https://community.infi niteflight.com/t/userdetails-
aspx-request/416101.
Done
Live API (blue)
Atlantic / pacifi c tracks
It would be great to be able to fetch the current tracks from infi nite flight. This could also include the new tracks that
Misha has been testing.
Done
Live API (blue)
Historical Data for Live API
See https://community.infi niteflight.com/t/historical-flights-in-userdetails-aspx/417261/2
Done
Live API (blue)
NOTAMS / TFR(s)
Be able to receive the current TFRs through the API.
Done
Live API (blue)
Get ATC operations gained from a particular controlling session
Done
Live API (blue)
Live API Airport Details Endpoint
See https://community.infi niteflight.com/t/new-api-airportdetails-aspx-request/417143.
Done
Live API (blue)
Flight time and range for current flight
Won't add
Live API (blue)
Request multiple flight plans through single request
A system for getting multiple flight plans all at once, similar to the current system for getting user information.
Won't add
Live API (blue)
Ability to Generate API Keys
Possibly through a developer center, anyone could be able to get their own API Key. Could be done through a review
and approve workflow.
Won't add
Live API (blue)
will fetch the stats of all pilots & ATC in the server in addition with
Won't add
Live API (blue)
Webhooks/Event Subscriptions
Implement a "don't call us, we'll call you" system for some events in the Live API. Possible events: - Certain User
Opened ATC Facility - Certain User Begins Flight - Certain User Closed ATC Facility - Certain User Ends Flight
Won't add
Live API (blue)
Multiple flight ids for flight plan endpoint.
Example: https://api.infi niteflight.com/public/v2/flight//flightplan?id=12312541&id=9877835&id=219873 Should be able to
fetch an array of flight plans for multiple users Original Request in IFC: https://community.infi niteflight.com/t/feature-
request-accept-multiple-flight-ids-for-get-flight-plan-endpoint/653702
Won't add
Live API (blue)
Request Multiple FPLs (Link to IFC)
This would be useful for getting ETAs for a list of flights, for example: flights inbound to an airport. More info below:
https://community.infi niteflight.com/t/feature-request-accept-multiple-flight-ids-for-get-flight-plan-endpoint/653702/20
Won't add
Live API (blue)
Get flight plan by IFC Name
Won't add
Live API (blue)
Get All Liveries - Include aircraft registration
We don't record this data and won't be adding this at this time. Sorry!
Won't add
Live API (blue)
et Flight Plan - Sending 0.0 lat/lng instead of null (see description
**0 is something. Null is nothing.** A null coordinate should be the proper way to tell if the API server had found
**nothing**. A zero coordinate can be interpreted as valid (such as latitudes along the equator).
Issues
Live API (blue)
Docs doesn't appropriately mention ALL nullable values (see des
It would also be better to mention if they can be null in the "Type" column and in the "Description" if there's any
additional info. This makes the API somewhat unpredictable. For example in the v2/sessions/{sessionId}/flights endpoint
the username can be null (not empty string) if the user is anonymous. Then it is reasonable to assume that v2/sessions/
{sessionId}/atc will also send back a null for the username (if needs be). But that is not the case. The API can send a
non-empty string with a "fake" username for presentation ("Controller"). Complete list of what I could get : v2/users :
UserStats - discourseUsername UserStats - virtualOrganization v2/sessions/{sessionId}/atc : ActiveATCFacility -
username ActiveATCFacility - virtualOrganization ActiveATCFacility - airportName v2/users/{userId}/atc/{atcSessionId} :
ATCFacility - airportIcao v2/sessions/{sessionId}/flights : FlightEntry - virtualOrganization FlightEntry - username v2/
sessions/{sessionId}/flights/{flightId}/flightplan : FlightPlanItem - name FlightPlanItem - children FlightPlanItem - identifi er
v2/tracks : OceanicTrack - eastLevels OceanicTrack - westLevels v2/users/{userId}/flights & v2/users/{userId}/atc :
PaginatedList - data v2/users/{userId}/flights & v2/users/{userId}/flights/{flightId} : UserFlight - liveryId (mentioned in
another issue) UserFlight - callsign v2/sessions/{sessionId}/notams : NotamResult - sessionId
Issues
Live API (blue)
Get User Flights - add violations received during flight
Feature Requests
Live API (blue)
Kafka Topic or any producer for IF events
https://community.infi niteflight.com/t/request-suggestion-a-kafka-topic-or-a-subscribable-stream-for-if-events/675603
Feature Requests
Live API (blue)
me fi eld (completely distinct from airportIcao) with the full name in
Feature Requests
Live API (blue)
Include a user's roles in the flights endpoint
Feature Requests
Live API (blue)
Search userIds with username regex expression
Feature Requests
Live API (blue)
Get a list of userIds by role
Get a list of userIds of specifi c groups such as IFATCs / mods / staff / other....
Feature Requests
Live API (blue)
Get Flights - Active / Away status
Feature Requests
Live API (blue)
HTTP POST) - Number of online ATC sessions (we have onlineFl
Feature Requests
Live API (blue)
Get User ATC Session(s) - Number of violations issued
Feature Requests
Live API (blue)
Get User ATC Session(s) - Server name
Feature Requests
Live API (blue)
een updates. Helps to perfectly sync with IF (example useful case
Feature Requests
Live API (blue)
ail - Fetch grade/other requirements (Get Sessions returns only if
Feature Requests
Live API (blue)
Get User Detail / Post User Stats - Number of online ATC sessions
Feature Requests
Live API (blue)
Get User Detail / Post User Stats - Total time ATC Sessions
Feature Requests
Live API (blue)
Get ATC Schedule
Feature Requests
Live API (blue)
s/{userId}/flights returning systematically null values for the liveryI
It seems that the liveryId returns a correct value for some people such as KaiM & Laura but for most people it seems
that it doesn't.
Done
Live API (blue)
ATC Actions for non-IFATC and Time Periods
In Live API UserDetails endpoint. Request by Chris_S via IFC. See https://community.infi niteflight.com/t/userdetails-
aspx-request/416101.
Done
Live API (blue)
Atlantic / pacifi c tracks
It would be great to be able to fetch the current tracks from infi nite flight. This could also include the new tracks that
Misha has been testing.
Done
Live API (blue)
Historical Data for Live API
See https://community.infi niteflight.com/t/historical-flights-in-userdetails-aspx/417261/2
Done
Live API (blue)
NOTAMS / TFR(s)
Be able to receive the current TFRs through the API.
Done
Live API (blue)
Get ATC operations gained from a particular controlling session
Done
Live API (blue)
Live API Airport Details Endpoint
See https://community.infi niteflight.com/t/new-api-airportdetails-aspx-request/417143.
Done
Live API (blue)
Flight time and range for current flight
Won't add
Live API (blue)
Request multiple flight plans through single request
A system for getting multiple flight plans all at once, similar to the current system for getting user information.
Won't add
Live API (blue)
Ability to Generate API Keys
Possibly through a developer center, anyone could be able to get their own API Key. Could be done through a review
and approve workflow.
Won't add
Live API (blue)
will fetch the stats of all pilots & ATC in the server in addition with
Won't add
Live API (blue)
Webhooks/Event Subscriptions
Implement a "don't call us, we'll call you" system for some events in the Live API. Possible events: - Certain User
Opened ATC Facility - Certain User Begins Flight - Certain User Closed ATC Facility - Certain User Ends Flight
Won't add
Live API (blue)
Multiple flight ids for flight plan endpoint.
Example: https://api.infi niteflight.com/public/v2/flight//flightplan?id=12312541&id=9877835&id=219873 Should be able to
fetch an array of flight plans for multiple users Original Request in IFC: https://community.infi niteflight.com/t/feature-
request-accept-multiple-flight-ids-for-get-flight-plan-endpoint/653702
Won't add
Live API (blue)
Request Multiple FPLs (Link to IFC)
This would be useful for getting ETAs for a list of flights, for example: flights inbound to an airport. More info below:
https://community.infi niteflight.com/t/feature-request-accept-multiple-flight-ids-for-get-flight-plan-endpoint/653702/20
Won't add
Live API (blue)
Get flight plan by IFC Name
Won't add
Live API (blue)
Get All Liveries - Include aircraft registration
We don't record this data and won't be adding this at this time. Sorry!
Won't add
Live API (blue)
et Flight Plan - Sending 0.0 lat/lng instead of null (see description
**0 is something. Null is nothing.** A null coordinate should be the proper way to tell if the API server had found
**nothing**. A zero coordinate can be interpreted as valid (such as latitudes along the equator).
Issues
Live API (blue)
Docs doesn't appropriately mention ALL nullable values (see des
It would also be better to mention if they can be null in the "Type" column and in the "Description" if there's any
additional info. This makes the API somewhat unpredictable. For example in the v2/sessions/{sessionId}/flights endpoint
the username can be null (not empty string) if the user is anonymous. Then it is reasonable to assume that v2/sessions/
{sessionId}/atc will also send back a null for the username (if needs be). But that is not the case. The API can send a
non-empty string with a "fake" username for presentation ("Controller"). Complete list of what I could get : v2/users :
UserStats - discourseUsername UserStats - virtualOrganization v2/sessions/{sessionId}/atc : ActiveATCFacility -
username ActiveATCFacility - virtualOrganization ActiveATCFacility - airportName v2/users/{userId}/atc/{atcSessionId} :
ATCFacility - airportIcao v2/sessions/{sessionId}/flights : FlightEntry - virtualOrganization FlightEntry - username v2/
sessions/{sessionId}/flights/{flightId}/flightplan : FlightPlanItem - name FlightPlanItem - children FlightPlanItem - identifi er
v2/tracks : OceanicTrack - eastLevels OceanicTrack - westLevels v2/users/{userId}/flights & v2/users/{userId}/atc :
PaginatedList - data v2/users/{userId}/flights & v2/users/{userId}/flights/{flightId} : UserFlight - liveryId (mentioned in
another issue) UserFlight - callsign v2/sessions/{sessionId}/notams : NotamResult - sessionId
Issues
Live API (blue)
Get User Flights - add violations received during flight
Feature Requests
Live API (blue)
Kafka Topic or any producer for IF events
https://community.infi niteflight.com/t/request-suggestion-a-kafka-topic-or-a-subscribable-stream-for-if-events/675603
Feature Requests
Live API (blue)
Card Name
Card Description
List Name
Labels
Card Name
Card Description
List Name
Labels
commands/reversethrust
this command doesn't appear to work (tested with no argument Int32, boolean, json structured identical to APIv1)
Issues
Connect (green)
simulator/throttle set and get are negative if each other
If you set simulator/throttle to a value x, then request the value and get a value y, y = -x. Set value of simulator/throttle:
100 Get value of simulator/throttle: -100
Issues
Connect (green)
Features Endpoint
TlL;DR: An `aircraft/0/features/*` endpoint would allow apps to see what capabilities an aircraft has. E.g.: `aircraft/0/
features/retractable_gear : True` and `aircraft/0/features/spoilers : False` for the TBM. This is a little more abstract. It’s
impossible to tell what capabilities an aircraft has right now. The C172 doesn’t have an endpoint for the Boeing MFD, but
it does have endpoints for things like spoilers, auto brakes, and even carrier ops. I’d like to be able to implement some
conditional logic, e.g. only show options for carrier ops if the current aircraft has a tail hook. Obviously this can be
worked around by hardcoding a tail hook option to be available for the F-18… but it becomes frustrating to hardcode
whether every aircraft in the fleet has spoilers, auto brakes, reverse thrust, retractable gear, etc. This option is also not
future-proof, as any future aircraft would need a confi guration defi ned in the third-party app. I suggest the creation of
`aircraft/0/features/*` endpoints for all these features that vary by aircraft. An alternative option would be to remove all
these endpoints for aircraft they don’t apply to. No need for the C172 to have a carrier ops endpoint exposed to me.
Feature Requests
Connect (green)
onnect v2 API comparable to "NetworkJoystick.SetNetworkJoystic
Feature Requests
Connect (green)
provide a better error response
Currently the api returns OK (Result = 0) with a TextRespones indicating error. Would be nice to either have it return
erorr, or return an error type, so it is easier to understand when invalid data has been sent
Feature Requests
Connect (green)
simulator/throttle/reverse
a get and set boolean state, in order to set reverse thrust on and off, e.g. setState(ID: "sim/throttle/reverse", value: true)
to activate reverse thrust
Feature Requests
Connect (green)
generic ATC command
Right now there's 10 separate ATC commands, no more, this makes it impossible to send higher values through the api.
Something like RunCommand(ID: "atcCommand", value: 12) which would send the ID of the ATC command, would help
Feature Requests
Connect (green)
en on the menu (infi niteflight/appstate and others are available in t
Feature Requests
Connect (green)
commands/togglemap
No way to show the map atm. Would be nice to have this, as well as zoom/motion and a state like mapIsShowing or
something
Feature Requests
Connect (green)
Select Aircraft as Controller in Connect API
As an ATC, you can currently send certain commands based on their number. However, you cannot select an aircraft to
send them to. See https://community.infi niteflight.com/t/select-aircraft-in-atc-interface/417256/2.
Feature Requests
Connect (green)
No way to tell if an aircraft has beacon (or other) lights.
Not all aircraft have beacon lights (TBM, A-10). There’s no difference in the api in this case — there are still all the same
endpoints. This is expandable in case an aircraft with less lights (e.g. a J-3 Cub) is added. Endpoints such as `aircraft/0/
has_beacon lights` for all the different lights would be helpful.
Feature Requests
Connect (green)
Way to return current camera from ConnectAPI
The api gives info on different cameras by number (I can look up the name of camera 4, for example) but there’s no way
to fi nd out the number of the current camera.
Feature Requests
Connect (green)
Ability to set time and date
Feature Requests
Connect (green)
UDP connections for flight control axes
UDP connection would allow for better latency of flight control commands. Sending camera commands via the UDP
SmoothTrack API is faster than sending them over TCP. I’d like to be able to continuously send flight control commands
the same way.
Feature Requests
Connect (green)
aircraft/0/weight
Feature Requests
Connect (green)
aircraft/0/mlw
Feature Requests
Connect (green)
aircraft/0/mtow
Feature Requests
Connect (green)
Opening up the Connect API for ATC
Feature Requests
Connect (green)
Ability to access functions of the editor
It would be cool to have access to different scenery editor functions via the connect API. Such as placing, modifying,
deleting, etc. The only one that I currently know of is the delete command. Even that still prompts the user to confi rm
though.
Feature Requests
Connect (green)
Get information about surrounding traffi c in Connect V2
Feature Requests
Connect (green)
aircraft/0/systems/nav_lights_switch endpoint is missing
This endpoint exists for the other three types of lights. It’s nice because it takes a boolean rather than a 1 or 0 int. A
workaround is to use aircraft/0/systems/electrical_switch/nav_lights_switch/state.
Done
Connect (green)
aircraft/0/systems/autopilot/on
This does not have setState functionality. Tested with Bools
Done
Connect (green)
n - Instantaneous gear descend/retract : aircraft/0/systems/landing
Done
Connect (green)
commands/Engine.Start and commands/Engine.Stop
These do not function. Tested with engine numbers as an argument
Done
Connect (green)
aircraft/0/systems/autopilot/spd/target
setState does not change the value of the autopilot spd target. Tested with float value.
Done
Connect (green)
commands/resetcamera
A command like this to recenter the camera (like on double tap) would be useful
Done
Connect (green)
Missing proper documentation
https://github.com/flyingdevelopmentstudio/infi niteflight-api Made by @philippe and @nicholas. Great starting point and
very helpful but outdated (? perhaps) and uncomplete.
Done
Connect (green)
state in the Connect v2 API to interrogate (and set) the rudder br
`aircraft/0/systems/brakes/left/percentage`
Done
Connect (green)
axis for dynamic braking
this has been added! `aircraft/0/systems/brakes/left/percentage`, and the right side too
Done
Connect (green)
Elevator trim direct setting state
available as: aircraft/0/systems/axes/elevator_trim
Done
Connect (green)
mmands/Pushback only attaches/detaches tug but doesn’t push ba
Won't add
Connect (green)
provide V1 api Command.SetGearState
I know it is old API, but would be a huge improvement Currently you can only toggle gear, so setting the gear to a
specifi c state requires another query to the aircraft state
Won't add
Connect (green)
commands/reversethrust
this command doesn't appear to work (tested with no argument Int32, boolean, json structured identical to APIv1)
Issues
Connect (green)
simulator/throttle set and get are negative if each other
If you set simulator/throttle to a value x, then request the value and get a value y, y = -x. Set value of simulator/throttle:
100 Get value of simulator/throttle: -100
Issues
Connect (green)
Features Endpoint
TlL;DR: An `aircraft/0/features/*` endpoint would allow apps to see what capabilities an aircraft has. E.g.: `aircraft/0/
features/retractable_gear : True` and `aircraft/0/features/spoilers : False` for the TBM. This is a little more abstract. It’s
impossible to tell what capabilities an aircraft has right now. The C172 doesn’t have an endpoint for the Boeing MFD, but
it does have endpoints for things like spoilers, auto brakes, and even carrier ops. I’d like to be able to implement some
conditional logic, e.g. only show options for carrier ops if the current aircraft has a tail hook. Obviously this can be
worked around by hardcoding a tail hook option to be available for the F-18… but it becomes frustrating to hardcode
whether every aircraft in the fleet has spoilers, auto brakes, reverse thrust, retractable gear, etc. This option is also not
future-proof, as any future aircraft would need a confi guration defi ned in the third-party app. I suggest the creation of
`aircraft/0/features/*` endpoints for all these features that vary by aircraft. An alternative option would be to remove all
these endpoints for aircraft they don’t apply to. No need for the C172 to have a carrier ops endpoint exposed to me.
Feature Requests
Connect (green)
onnect v2 API comparable to "NetworkJoystick.SetNetworkJoystic
Feature Requests
Connect (green)
provide a better error response
Currently the api returns OK (Result = 0) with a TextRespones indicating error. Would be nice to either have it return
erorr, or return an error type, so it is easier to understand when invalid data has been sent
Feature Requests
Connect (green)
simulator/throttle/reverse
a get and set boolean state, in order to set reverse thrust on and off, e.g. setState(ID: "sim/throttle/reverse", value: true)
to activate reverse thrust
Feature Requests
Connect (green)
generic ATC command
Right now there's 10 separate ATC commands, no more, this makes it impossible to send higher values through the api.
Something like RunCommand(ID: "atcCommand", value: 12) which would send the ID of the ATC command, would help
Feature Requests
Connect (green)
en on the menu (infi niteflight/appstate and others are available in t
Feature Requests
Connect (green)
commands/togglemap
No way to show the map atm. Would be nice to have this, as well as zoom/motion and a state like mapIsShowing or
something
Feature Requests
Connect (green)
Select Aircraft as Controller in Connect API
As an ATC, you can currently send certain commands based on their number. However, you cannot select an aircraft to
send them to. See https://community.infi niteflight.com/t/select-aircraft-in-atc-interface/417256/2.
Feature Requests
Connect (green)
No way to tell if an aircraft has beacon (or other) lights.
Not all aircraft have beacon lights (TBM, A-10). There’s no difference in the api in this case — there are still all the same
endpoints. This is expandable in case an aircraft with less lights (e.g. a J-3 Cub) is added. Endpoints such as `aircraft/0/
has_beacon lights` for all the different lights would be helpful.
Feature Requests
Connect (green)
Way to return current camera from ConnectAPI
The api gives info on different cameras by number (I can look up the name of camera 4, for example) but there’s no way
to fi nd out the number of the current camera.
Feature Requests
Connect (green)
Ability to set time and date
Feature Requests
Connect (green)
UDP connections for flight control axes
UDP connection would allow for better latency of flight control commands. Sending camera commands via the UDP
SmoothTrack API is faster than sending them over TCP. I’d like to be able to continuously send flight control commands
the same way.
Feature Requests
Connect (green)
aircraft/0/weight
Feature Requests
Connect (green)
aircraft/0/mlw
Feature Requests
Connect (green)
aircraft/0/mtow
Feature Requests
Connect (green)
Opening up the Connect API for ATC
Feature Requests
Connect (green)
Ability to access functions of the editor
It would be cool to have access to different scenery editor functions via the connect API. Such as placing, modifying,
deleting, etc. The only one that I currently know of is the delete command. Even that still prompts the user to confi rm
though.
Feature Requests
Connect (green)
Get information about surrounding traffi c in Connect V2
Feature Requests
Connect (green)
aircraft/0/systems/nav_lights_switch endpoint is missing
This endpoint exists for the other three types of lights. It’s nice because it takes a boolean rather than a 1 or 0 int. A
workaround is to use aircraft/0/systems/electrical_switch/nav_lights_switch/state.
Done
Connect (green)
aircraft/0/systems/autopilot/on
This does not have setState functionality. Tested with Bools
Done
Connect (green)
n - Instantaneous gear descend/retract : aircraft/0/systems/landing
Done
Connect (green)
commands/Engine.Start and commands/Engine.Stop
These do not function. Tested with engine numbers as an argument
Done
Connect (green)
aircraft/0/systems/autopilot/spd/target
setState does not change the value of the autopilot spd target. Tested with float value.
Done
Connect (green)
commands/resetcamera
A command like this to recenter the camera (like on double tap) would be useful
Done
Connect (green)
Missing proper documentation
https://github.com/flyingdevelopmentstudio/infi niteflight-api Made by @philippe and @nicholas. Great starting point and
very helpful but outdated (? perhaps) and uncomplete.
Done
Connect (green)
state in the Connect v2 API to interrogate (and set) the rudder br
`aircraft/0/systems/brakes/left/percentage`
Done
Connect (green)
axis for dynamic braking
this has been added! `aircraft/0/systems/brakes/left/percentage`, and the right side too
Done
Connect (green)
Elevator trim direct setting state
available as: aircraft/0/systems/axes/elevator_trim
Done
Connect (green)
mmands/Pushback only attaches/detaches tug but doesn’t push ba
Won't add
Connect (green)
provide V1 api Command.SetGearState
I know it is old API, but would be a huge improvement Currently you can only toggle gear, so setting the gear to a
specifi c state requires another query to the aircraft state
Won't add
Connect (green)
commands/reversethrust
this command doesn't appear to work (tested with no argument Int32, boolean, json structured identical to APIv1)
Issues
Connect (green)
simulator/throttle set and get are negative if each other
If you set simulator/throttle to a value x, then request the value and get a value y, y = -x. Set value of simulator/throttle:
100 Get value of simulator/throttle: -100
Issues
Connect (green)
Features Endpoint
TlL;DR: An `aircraft/0/features/*` endpoint would allow apps to see what capabilities an aircraft has. E.g.: `aircraft/0/
features/retractable_gear : True` and `aircraft/0/features/spoilers : False` for the TBM. This is a little more abstract. It’s
impossible to tell what capabilities an aircraft has right now. The C172 doesn’t have an endpoint for the Boeing MFD, but
it does have endpoints for things like spoilers, auto brakes, and even carrier ops. I’d like to be able to implement some
conditional logic, e.g. only show options for carrier ops if the current aircraft has a tail hook. Obviously this can be
worked around by hardcoding a tail hook option to be available for the F-18… but it becomes frustrating to hardcode
whether every aircraft in the fleet has spoilers, auto brakes, reverse thrust, retractable gear, etc. This option is also not
future-proof, as any future aircraft would need a confi guration defi ned in the third-party app. I suggest the creation of
`aircraft/0/features/*` endpoints for all these features that vary by aircraft. An alternative option would be to remove all
these endpoints for aircraft they don’t apply to. No need for the C172 to have a carrier ops endpoint exposed to me.
Feature Requests
Connect (green)
onnect v2 API comparable to "NetworkJoystick.SetNetworkJoystic
Feature Requests
Connect (green)
provide a better error response
Currently the api returns OK (Result = 0) with a TextRespones indicating error. Would be nice to either have it return
erorr, or return an error type, so it is easier to understand when invalid data has been sent
Feature Requests
Connect (green)
simulator/throttle/reverse
a get and set boolean state, in order to set reverse thrust on and off, e.g. setState(ID: "sim/throttle/reverse", value: true)
to activate reverse thrust
Feature Requests
Connect (green)
generic ATC command
Right now there's 10 separate ATC commands, no more, this makes it impossible to send higher values through the api.
Something like RunCommand(ID: "atcCommand", value: 12) which would send the ID of the ATC command, would help
Feature Requests
Connect (green)
en on the menu (infi niteflight/appstate and others are available in t
Feature Requests
Connect (green)
commands/togglemap
No way to show the map atm. Would be nice to have this, as well as zoom/motion and a state like mapIsShowing or
something
Feature Requests
Connect (green)
Select Aircraft as Controller in Connect API
As an ATC, you can currently send certain commands based on their number. However, you cannot select an aircraft to
send them to. See https://community.infi niteflight.com/t/select-aircraft-in-atc-interface/417256/2.
Feature Requests
Connect (green)
No way to tell if an aircraft has beacon (or other) lights.
Not all aircraft have beacon lights (TBM, A-10). There’s no difference in the api in this case — there are still all the same
endpoints. This is expandable in case an aircraft with less lights (e.g. a J-3 Cub) is added. Endpoints such as `aircraft/0/
has_beacon lights` for all the different lights would be helpful.
Feature Requests
Connect (green)
Way to return current camera from ConnectAPI
The api gives info on different cameras by number (I can look up the name of camera 4, for example) but there’s no way
to fi nd out the number of the current camera.
Feature Requests
Connect (green)
Ability to set time and date
Feature Requests
Connect (green)
The API responses being compatible in multiple languages.
Some people in our development may not understand english well. For example, the json responses will appear in
another language like french. As apart of this, add endpoints which allows users to change the language of their data.
for example: /v2/sessions?apikey={apikey}&lang=cn (for chinese) or /v2/sessions?apikey={apikey}&lang=de (for
german)
Feature Requests
Infi nite Flight OAuth system (@see description)
Similar to Sign in with Google. Users can sign in using their Infi nite Flight account. The API would expose their discourse
username, email and profi le picture. It would be especially useful when syncing up their IF account to a third party app
(in the easiest way possible).
Feature Requests
GetUserStats - Level 2/3 Count
Add Level 2/3 count for 24 hours to the GetUserStats endpoint similar to the old api with the 24 hour ghosting. This will
save going to the grade endpoint.
Done
The API responses being compatible in multiple languages.
Some people in our development may not understand english well. For example, the json responses will appear in
another language like french. As apart of this, add endpoints which allows users to change the language of their data.
for example: /v2/sessions?apikey={apikey}&lang=cn (for chinese) or /v2/sessions?apikey={apikey}&lang=de (for
german)
Feature Requests
Infi nite Flight OAuth system (@see description)
Similar to Sign in with Google. Users can sign in using their Infi nite Flight account. The API would expose their discourse
username, email and profi le picture. It would be especially useful when syncing up their IF account to a third party app
(in the easiest way possible).
Feature Requests
GetUserStats - Level 2/3 Count
Add Level 2/3 count for 24 hours to the GetUserStats endpoint similar to the old api with the 24 hour ghosting. This will
save going to the grade endpoint.
Done
