Navigraph API Request Followup

Hey Navigraph team,

I am currently working on a side project (flight tracker) that has some use cases for some of the services offered by the Navigraph API.

I had written to dev@navigraph.com, got approval, and Markus had suggested that I needed two clients for my use cases, one client for the desktop application to authenticate via the Device Authorization Flow, and another for the mobile application to authenticate via the Authorization Code Flow.

Since then I’ve only received credentials for the Authorization Code Flow client, with the following scopes: [“openid”, “simbrief”, “ofp”, “offline_access”], which doesn’t include the “fmsdata” scope I had requested for my use case (parsing routes to render them correctly on the map; I also tested making a call to fetch the fmsdata, which does return 200 but with an empty array - not sure if I am doing something wrong on my end).

I’ve sent followups regarding this + to inquire regarding the process for getting access to the AMDB API as well (currently relying on OSM data for rendering airports, would like to use AMDB for users Navigraph subscriptions).

I’ve read multiple forum posts discussing emails that have failed to arrive, etc; I understand that there are different factors that affect the response time especially with the volume of requests you guys must be getting, so I just wanted to ensure that my communication wasn’t lost.

Thanks.

Nevermind, Markus just got back to me with everything I needed in detail! :slight_smile: Now I’m just looking for the docs for the new simbrief API and I’ll be all set!