Skip to main content
Pilots and club members use one Volanti account for Volanti, Events.Aero and Split My Flight. Your application can let them sign in with it too, so they have no new password to set up, and you can read their name and email address once they approve. It’s a standard OAuth 2.0 authorisation server, so most OAuth libraries work with it as they are.

Getting access

Volanti issues OAuth clients by arrangement, so there’s no self-service registration. Email [email protected] with your application’s name and its redirect URL, and we’ll send you a client ID (and a client secret, if your application can keep one private).

The flow

Sign in uses the authorisation code flow. Applications that can’t keep a secret (a mobile app, a single-page app) add PKCE with the S256 method.
1

Send the person to Volanti

Redirect them to the authorisation endpoint:
Leave out the two code_challenge parameters if your client has a secret.
2

They sign in and approve

Volanti asks them to sign in, then to approve your application. They come back to your redirect_uri with code and your state. Check that state matches the value you sent.
3

Exchange the code for tokens

A public client sends code_verifier instead of client_secret.
4

Ask who signed in

Call Get authenticated user with the access token:

Token lifetimes

When an access token expires, get a new one from the same token endpoint with grant_type=refresh_token and the refresh token.

What this covers

This reference covers signing a person in and reading their profile. Identity has no other public endpoints.