Skip to main content
The sandbox lives on the AWS dev environment of MyPilotIndex. It holds ten synthetic pilots and no real member. A sandbox partner connects them the way it will connect real pilots, so you can test the consent, the summary and the push of flight totals before you reach a member.

​
The synthetic pilots

  • There are ten pilots, “Sandbox Pilot 1” to “Sandbox Pilot 10”, each with an account of its own.
  • Their flight hours grow from the first pilot (150 hours) to the tenth (4,200 hours); turbine time appears from the fifth and jet time from the seventh.
  • Each holds the FAA private pilot license and has a score computed from that record.
  • All ten share one sign-in password. We give it to sandbox partners with the credential; it is never published.

​
Connecting a synthetic pilot

  1. Operators register your partner and create your client. You receive the client id, the client secret, the sandbox API host and the identity provider’s dev domain.
  2. Get a token from the dev domain’s /oauth2/token with the client credentials grant.
  3. Send a browser to the consent page of the dev environment, /connect/{slug} with the usual parameters, and sign in as one of the sandbox pilots with the shared password. Then allow.
  4. Exchange the code at the sandbox API host and call the Partner API with the grant.
The dev environment accepts partners registered as sandbox and partners that are active. A partner registered as sandbox works on the dev environment only: its credential does not work in production, and production access is granted separately after review.