Skip to content

Authentication

Authentication is a crucial part of interacting with the Prusa Connect API. The SDK handles authentication tokens automatically once you've logged in.

How it Works

The SDK uses the same OAuth 2.0 flow as the official Prusa Connect web interface to obtain access and refresh tokens. It uses the PKCE (Proof Key for Code Exchange) extension to securely obtain tokens without a client secret (kudos to the Prusa Connect team for doing things right and implementing this! 🌟).

  1. Identity Token: Provides identity information about the user.
  2. Access Token: Used to authenticate API requests. Valid for a short period (usually 1 hour).
  3. Refresh Token: Used to obtain new access tokens when they expire. Valid for a longer period (usually 30 days).

Storing Credentials

The SDK stores tokens securely in a user-specific configuration directory using platformdirs.

  • Linux: ~/.config/prusa-connect-sdk-client/tokens.json (or similar)
  • macOS: ~/Library/Application Support/prusa-connect-sdk-client/tokens.json
  • Windows: %APPDATA%\prusa-connect-sdk-client\tokens.json

The file is JSON-formatted and contains the tokens. It is recommended to restrict access to this file.

Authentication Methods

Run prusactl auth login to start an interactive login session. This will prompt for your email, password, and 2FA code (if enabled).

2. Environment Variables

You can also provide credentials via environment variables, although this is generally less secure for long-term use.

  • PRUSA_EMAIL: Your Prusa Account email.
  • PRUSA_PASSWORD: Your Prusa Account password.

Note: Environment variables are used for initial login if provided, but tokens are preferred.

3. Headless / CI/CD Authentication

For automated environments where interactive login isn't possible, set one of the following environment variables. PrusaConnectClient detects them automatically — no call to auth login required.

Variable Value
PRUSA_TOKEN Raw JWT access token string (ey...)
PRUSA_TOKENS_JSON Full token JSON object (access + refresh tokens) 
export PRUSA_TOKEN="ey..."

export PRUSA_TOKENS_JSON='{"access_token": "ey...", "refresh_token": "ey..."}'

Getting the raw token

Run prusactl auth print-access-token to print the current access token to stdout. This is useful for seeding PRUSA_TOKEN in a secrets manager or CI environment variable.

4. Programmatic Authentication

You can use prusa.connect.client.auth.interactive_login to perform the login flow in your own application. See the SDK Quickstart for an example.