Skip to main content

Authentication

The Airborne Core CLI authenticates with a bearer token. You obtain the token by exchanging a client ID and client secret through the PostLogin command, then supply that token to every other operation via the --token parameter.

note

Run configure --base-url before authenticating, so the CLI knows which Airborne API to talk to.

Getting client credentials​

Generate a client ID and client secret from the Airborne dashboard. See access tokens in the dashboard for how to create and manage them.

Obtaining a token with PostLogin​

airborne-core-cli PostLogin --client_id <client-id> --client_secret <client-secret>

Parameters:

ParameterTypeRequiredDescription
--client_idstringYesClient ID provided by Airborne.
--client_secretstringYesClient Secret provided by Airborne.

On success, PostLogin returns a JSON response containing an access token (and a refresh token). Copy the access token value — you pass it to other commands as --token.

You can also supply the credentials through a JSON parameters file:

airborne-core-cli PostLogin @login.json

Where login.json contains:

{
  "client_id": "your_client_id",
  "client_secret": "your_client_secret"
}
note

Unlike the React Native CLI, the Core CLI does not persist the token to disk for you. PostLogin returns the token; capturing and reusing it is up to you. The React Native CLI's login command wraps this same operation and stores the result automatically.

Using the token​

Pass the access token to any authenticated operation with --token:

airborne-core-cli ListOrganisations --token <access-token>

airborne-core-cli CreateApplication \
  --application myapp \
  --organisation myorg \
  --token <access-token>

The --token parameter is required on every operation except PostLogin and configure. You can also include it in a JSON parameters file:

{
  "organisation": "myorg",
  "application": "myapp",
  "token": "your_access_token_here"
}

In scripts, capture the token into an environment variable and reference it:

airborne-core-cli ListReleases \
  --organisation myorg \
  --application myapp \
  --token "$AIRBORNE_TOKEN"
caution

Treat the access token and your client credentials as secrets. Do not commit them to version control; prefer environment variables or a secure secret store in CI.

Next​