Skip to main content
The SDK lets you generate workspace tokens that authenticate the CLI without an interactive browser login. This is the bridge between backend provisioning and filesystem mounting — your backend creates the workspace and token, then passes the token to a VM or CI runner that mounts the filesystem.

Create a mount token

The raw token value is only returned at creation time. Store it securely — you won’t be able to retrieve it again.

Mount on a VM

Once you have a token, pass it to the CLI to mount without a browser:
Or run as a background daemon:
This is ideal for headless Linux VMs, CI runners, or any environment without a browser.

Token with expiration

Set expiresIn to 0 (or omit it) for tokens that don’t expire.

List tokens

Token listing returns metadata only. Raw token values are never exposed after creation.

Revoke a token

Revoked tokens stop working immediately. Any CLI sessions using that token will disconnect.

Full provisioning flow

Here’s a complete example: create a workspace, connect an integration, set up a source view, and return a mount token:

Next steps

CLI reference

Full airstore mount and airstore start docs.

Tokens reference

Full method reference for client.tokens.