overlane auth token | Overlane Docs

Prints the token the other commands would use: the stored sign-in. It is a credential. Pipe it into the tool that needs it; never paste it into a chat, a file or a command line. overlane auth status reports the same facts without the token. Exit 3 when there is none.

Usage

overlane auth token [--service URL]

Flags

Flag	Type	Required	Default	Description
`--service`	string	no		The service address (default: OVERLANE_SERVICE_URL, then the project’s binding, then the hosted service)

Examples

overlane auth token
overlane auth token --json

Behavior

Effect: read (changes nothing).
Needs credentials: yes. Uses the network: no.
Supports --dry-run: no. Accepts --force: no.
Machine-readable description: overlane schema auth token.

Result

With --json (the default when stdout is not a terminal) the command prints this JSON Schema’s shape on stdout.

{
  "type": "object",
  "properties": {
    "token": {
      "type": "string"
    },
    "how": {
      "type": "string",
      "enum": [
        "keychain",
        "file"
      ]
    },
    "expiresAt": {
      "type": "string"
    }
  },
  "required": [
    "token",
    "how"
  ],
  "additionalProperties": false
}

See exit codes for the status the process returns.