Tooling
CLI sign-in
The device code flow behind reintersect login.
POST
CLI sign-in
reintersect login signs in with a device code, like gh auth login. Three endpoints take part.
Start: POST /v0/cli/device
Needs no credential. The body is { host }, a short name for the computer (letters, digits, ., _
and -, up to 63 characters). It responds with:
Poll: POST /v0/cli/device/token
Needs no credential. The body is { deviceCode }. Until the member confirms, it fails with
ReintersectCliAuthorizationPendingError (400) or ReintersectCliSlowDownError (400, with a new
interval). After that, it fails with ReintersectCliDeviceCodeExpiredError or
ReintersectCliAccessDeniedError, or answers with:
Session: GET /v0/cli/session
Authenticate with a member API key or a deploy token. The response says who the credential belongs
to:
{ kind: "member", member, workspace } or { kind: "deploy", appId, repository, ref, previewOnly }.