How Can I Transfer the License Key to PTV Navigator G2?

Applies to: PTV Navigator G2 administrators and developers — choosing how to get a license key onto a device.

PTV Navigator G2 needs a valid license key to run. There are four ways to provide one, and the right choice depends mostly on fleet size and whether devices run your own app alongside PTV Navigator G2.

Which approach fits?

1. Scan a QR code

The simplest option: scan a QR code containing the license key directly on the device's login screen. No setup, no integration — good for testing or a handful of devices. It doesn't scale, though: every device needs someone physically scanning a code (and license keys are long, ~92-character strings, not practical to type by hand), so this isn't a practical option once you're beyond a very small fleet.

2. Managed Configurations (MDM)

The standard option for fleets managed through an MDM. PTV Navigator G2 (v1.1.0 and later) supports Android Enterprise Managed Configurations — your MDM pushes the license key to every device as part of the regular app rollout, with no manual entry or per-device interaction. This is the most scalable option, and the one we recommend once you're managing more than a handful of devices.

Full reference: Managed Configurations documentation.

3. Android Intent

For devices where your own app — a driver app, a launcher, a kiosk shell — runs alongside PTV Navigator G2. Your app sends a single Android Intent (licensekey:<yourLicenseKey>) to hand over the key. It's a one-way handoff: PTV Navigator G2 checks the key and applies it if valid (keeping the previous key if the check fails), but doesn't report the result back to your app through the Intent itself.

Full reference: Android Intents guide.

4. Remote Interface / API

Also for devices running your own app alongside PTV Navigator G2, but for cases where you need confirmation or want licensing to go through the same channel as other integrations. The Remote Interface is a bidirectional connection: your app sends the license key command and gets an acknowledgement back, so you know immediately whether it was accepted. Beyond setting a key, it also lets your app actively log a device out — useful when decommissioning a device or reassigning its license to another one. Makes the most sense if you're already using the Remote Interface for other things — vehicle profiles, navigation control — and want licensing handled the same way.

Full reference: API documentation — licensing-related commands.