---
title: "pando login, step 1: a code to confirm in the browser"
description: "Starts WorkOS CLI Auth. Show `user_code` and `verification_uri` (or\nopen `verification_uri_complete`). Keep `device_code` to yourself: it\nis what the CLI polls with. No credential needed.\n"
---

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

Path: Pando API › users

`POST /v1/login/device`

Starts WorkOS CLI Auth. Show `user_code` and `verification_uri` (or
open `verification_uri_complete`). Keep `device_code` to yourself: it
is what the CLI polls with. No credential needed.

## Code samples

### cURL

```curl
curl --request POST \
  --url https://app.gitpando.com/v1/login/device
```

### TypeScript

```typescript
const url = 'https://app.gitpando.com/v1/login/device';
const options = {method: 'POST'};

fetch(url, options)
  .then(res => res.json())
  .then(json => console.log(json))
  .catch(err => console.error(err));
```

### Python

```python
import requests

url = "https://app.gitpando.com/v1/login/device"

response = requests.post(url)

print(response.text)
```

## Responses

### 200

OK

#### Example

```json
{
  "device_code": "string",
  "user_code": "string",
  "verification_uri": "string",
  "verification_uri_complete": "string",
  "expires_in": 0,
  "interval": 0
}
```

- `loginStart.response.200.device_code` (string, required)
- `loginStart.response.200.user_code` (string, required) — For example `RRGQ-BJVS`.
- `loginStart.response.200.verification_uri` (string, required)
- `loginStart.response.200.expires_in` (integer, required) — Seconds, usually 300.
- `loginStart.response.200.interval` (integer, required) — Seconds between polls, usually 5.
- `loginStart.response.200.verification_uri_complete` (string, optional)

### 503

`sign_in_not_configured`: WORKOS_CLIENT_ID is not set on this Worker (use the bootstrap path).

#### Example

```json
{
  "error": {
    "code": "string",
    "message": "string",
    "paths": [
      "string"
    ],
    "checks": {
      "sha": "string",
      "state": "success",
      "required": [
        "string"
      ],
      "checks_unknown": "string",
      "missing": [
        "string"
      ],
      "statuses": [
        {
          "sha": "string",
          "context": "string",
          "state": "pending",
          "target_url": "string",
          "description": "string",
          "creator": "string",
          "app": "string",
          "created_at": "2019-08-24T14:15:22Z"
        }
      ]
    }
  }
}
```

- `loginStart.response.503.error` (object, required)
  - `loginStart.response.503.error.code` (string, required)
  - `loginStart.response.503.error.message` (string, required)
  - `loginStart.response.503.error.paths` (array<string>, optional)
  - `loginStart.response.503.error.checks` (object, optional) — GitHub's combined status, plus the required contexts and which are missing.
    - `loginStart.response.503.error.checks.sha` (string | null, required)
    - `loginStart.response.503.error.checks.state` (string, required) — `success` when the merge gate passes; `missing` when a required context has not reported; `unknown` while the required checks are (an unforced merge is refused).
      - one of `"success"`, `"pending"`, `"failure"`, `"error"`, `"missing"`, `"unknown"`
    - `loginStart.response.503.error.checks.required` (array | null, required) — Null while unknown.
    - `loginStart.response.503.error.checks.checks_unknown` (string | null, required) — Why the required checks are unknown, in plain words: "Pando couldn't read this monorepo's required checks; try again", or "pando.toml line 3: expected comma or end of structure; fix it on main, or merge with force". Null otherwise.
    - `loginStart.response.503.error.checks.statuses` (array<object>, required) — The latest status per context.
      - `loginStart.response.503.error.checks.statuses.sha` (string, required)
      - `loginStart.response.503.error.checks.statuses.context` (string, required)
      - `loginStart.response.503.error.checks.statuses.state` (string, required)
        - one of `"pending"`, `"success"`, `"failure"`, `"error"`
      - `loginStart.response.503.error.checks.statuses.created_at` (string, required)
        - format `date-time`
      - `loginStart.response.503.error.checks.statuses.target_url` (string | null, optional)
      - `loginStart.response.503.error.checks.statuses.description` (string | null, optional)
      - `loginStart.response.503.error.checks.statuses.creator` (string, optional) — The member who posted it (a login); `app:<slug>` for a status posted with a status token or by a CI integration; `hook:<hook id>` for a status token from a web hook with no app.
      - `loginStart.response.503.error.checks.statuses.app` (string | null, optional) — The CI service that reported it (`buildkite`, `github-actions`, ...), stamped by Pando from a status token or a CI integration, never from the body or `target_url`. Null when a member posted it with their own credential. The web shows the service's mark for a slug it knows.
    - `loginStart.response.503.error.checks.missing` (array<string>, optional)


Source: https://docs.gitpando.com/api/users/loginStart/index.md