---
title: "overlane auth token"
description: "Print the access token in use, for scripts (a secret: handle with care)"
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.overlane.app/llms.txt
> Use this file to discover all available pages before exploring further.

# overlane auth token

{/* Generated by apps/docs/scripts/generate.mjs (CLI pages from the command registry in packages/cli). Do not edit; run `pnpm --filter @overlane/docs gen`. */}

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

```sh
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

```sh
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.

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

See [exit codes](/cli/#exit-codes) for the status the process returns.

Source: https://docs.overlane.app/cli/auth-token/index.mdx