import
Flights your app adds
Your app adds flights to the logbook, and changes or removes the flights it added itself. It cannot read the logbook and cannot touch anything else in it. Every approved app has this level.
Developers
Build on a pilot's logbook.
Apps can add flights to a Jetlog logbook, and with the pilot's permission read it. You register your app and we review it. After that, your app can send pilots to Jetlog, where they approve it in the Jetlog app.
Access
Two levels, and the pilot picks.
Every app starts with the ability to add flights, and to change or remove the flights it added. Reading the whole logbook is a second level that Jetlog switches on per app. Even then the pilot chooses which level to give when connecting.
import read write
Whole logbook
Your app reads flights, people, aircraft and totals. Flights it adds still go in directly. A change to anything the app did not add is only a proposal: it waits until the pilot approves it in the Jetlog app, so nothing is changed behind the pilot's back. An app can propose changes to flights and crew, and only to what the pilot can be shown. Files, photos and signatures are never available.
You ask for this level on your app's page in the console, with a short reason. Jetlog decides per app.
How it works
From registration to a connected pilot.
-
Register your app
Sign in to the console with the email address of your Jetlog account. Publish a small JSON file on your own domain that names your app and lists its redirect addresses. Its address is your client_id. The console gives you a verification value to put in that file, so we know the file is yours, and checks the file for you before you submit.
-
We review it
Jetlog reviews every app. We fetch your file again before approving, and you get an email with the decision. Until then pilots cannot connect the app.
-
Pilots connect it
Your app sends the pilot to Jetlog to sign in and approve, with the standard OAuth authorization code flow and PKCE. There is no client secret. Access tokens last an hour, refresh tokens 90 days and change on every use. A pilot can disconnect your app at any time in the Jetlog app.
The console
See how your app is doing.
Once your app is registered, its page in the console shows where the review stands, and after approval how the app is used.
- Status
- Whether your app is waiting for review, approved, disabled or not approved, and why.
- Pilots
- How many pilots have your app connected. You see a count, never who they are.
- Requests
- Requests per day for the last 30 days, split by import, read and changes, with the errors your app got and how often the rate limit stopped it.
- Whole logbook
- Whether your app has it, and a form to ask for it.
Reference
The API
Endpoints, payloads, token handling and the errors your app can get.
Open the reference →Sample app
A working example
A small web app that connects to your own Jetlog account, so you can see the whole flow run.
Open the sample →Console
Register your app
You need a Jetlog account. Create one in the app first if you do not have one yet.
Open the console →Good to know
- Redirect addresses must be https. A phone app uses a link it has claimed (a universal link on iOS, an App Link on Android). Custom schemes such as myapp:// are not accepted. While you develop you can use a loopback address such as http://127.0.0.1:8787/callback.
- Your app name is shown to pilots when they approve it. It is plain text of at most 64 characters, and names that contain "Jetlog" are not available.
- You can have up to five apps. After you submit an app you cannot change its name or address. Register a new app, or write to support@jetlog.app.
- Jetlog applies rate limits. When your app is stopped it gets a 429 answer with a Retry-After header.
Ready to register your app?
Sign in with your Jetlog account and register your app in a few minutes.