# Navigation Data API Client ID request for CAVacars 2 (Canada Air Virtual)

**URL:** <https://forum.navigraph.com/t/navigation-data-api-client-id-request-for-cavacars-2-canada-air-virtual/24728>\
**Category:** API\
**Created:** [November 3, 2026, 5:37am UTC](https://forum.navigraph.com/t/navigation-data-api-client-id-request-for-cavacars-2-canada-air-virtual/24728 "2026-11-03T05:37:33Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![ChalkOne](https://avatars.discourse-cdn.com/v4/letter/c/e36b37/32.png) [@ChalkOne](https://forum.navigraph.com/u/ChalkOne)\
**Post date:** [November 3, 2026, 5:37am UTC](https://forum.navigraph.com/t/navigation-data-api-client-id-request-for-cavacars-2-canada-air-virtual/24728/1 "2026-11-03T05:37:33Z")

</div>

Hello Navigraph Development Team,

I’m the developer of Canada Air Virtual ([https://canadaairvirtual.ca](https://canadaairvirtual.ca)), a non-commercial virtual airline for flight simulator pilots. I emailed a Navigation Data API Client ID request for our flight-tracking client, CAVacars 2, to [dev@navigraph.com](mailto:dev@navigraph.com) on October 5 and followed up about 2 weeks past that. I know you’re working through a backlog, so this is just a polite follow-up in case it’s easier to pick up here.

**What we’d use it for**

- Expanding a filed route string (SID, airways, waypoints, STAR) into coordinates, so the moving map shows the planned route as a line under the live aircraft position instead of a straight line between airports.
- Showing the fixes of the selected departure, arrival and approach procedures along that route.
- Looking up airport and runway information for the departure, arrival and alternate airports during flight tracking.
- This is an optional feature for pilots who already have their own Navigraph subscription. Pilots without one continue to use our existing free data sources.

**About the app**

CAVacars 2 is a desktop ACARS client for our pilots (Electron; Windows, with macOS/Linux builds). It supports MSFS, FSX/Prepar3D and X-Plane, and runs alongside the simulator on the pilot’s PC or local network. We are not requesting Charts API access, and we don’t plan to draw anything that resembles a chart.

**How data is handled**

- Each pilot links their own Navigraph account in the app’s settings using the Device Authorization Flow with PKCE. Tokens are stored locally on the pilot’s machine and never sent to our servers.
- Each client downloads the package directly with the pilot’s own token. There is no server-side proxy, and nothing is shared between pilots or stored on our servers.
- The client checks the packages endpoint at most once per day and keeps the package only in the local application cache.
- If a pilot’s subscription lapses, the client uses whatever package the API returns for that account, and we delete stored data if access is revoked.
- Navigraph data is used only for flight simulation, never for real-world navigation.

**What we’re asking for**

A Client ID for the Navigation Data API, with the DFD v2 (SQLite) format if possible. No redirect URI is needed, since we use the device flow.

Canada Air Virtual is free for pilots. Happy to share more detail or a demo build if that helps.

Thank you!  
Jan