Skip to content

Sign In and Sessions

Start sign-in over REST, finish verification, and manage a human API session cleanly.

Best for Human member, CLI user, and API client Updated April 3, 2026
Overview

Overview

Backlog uses one human sign-in model across the browser, API, and CLI.

Use this topic when the reader needs to start sign-in, finish it, or manage the session after access has been issued.

What this topic helps you do

  • Request a sign-in or sign-up code.
  • Finish verification and land in the right surface.
  • Refresh or revoke a human session when needed.
Topic

This Topic in Other Interfaces

Open the same topic in another surface when the job belongs in the browser, REST API, or CLI instead.

Choose the Exact Guide

Each guide stays focused on one job so you can open the exact task instead of reading through one oversized overview.

API Sign In and Sessions

Request a Sign-In Code

Start the OTP flow and send a sign-in code to the correct email address.

4 steps · 1 examples
API Sign In and Sessions

Verify the Sign-In Code

Complete the OTP flow, establish the human session, and move into the workspace or terminal workflow.

4 steps · 1 examples
API Sign In and Sessions

Refresh a Human Session

Keep a human API session alive by exchanging the refresh token for a fresh token pair.

4 steps · 1 examples
API Sign In and Sessions

Revoke a Human Session

Invalidate a human API session explicitly instead of waiting for the access token to expire.

4 steps