Skip to main content

Authentication

Session Authentication

The primary authentication method is session-based via NextAuth. When signed in through the web application, API requests from the same browser session are automatically authenticated via cookies.

API Key Authentication

Organization administrators can create REST API keys for programmatic access. Keys follow the format thig_ + 40 hexadecimal characters. Include the API key in the Authorization header:
All 225+ API endpoints support API key authentication — no special configuration needed per endpoint.

Key Management

Create and manage API keys at Settings > Developer (/admin/settings/developer) or via the API:

Rate Limits

API keys are rate-limited to 60 requests per minute by default. Enterprise plans can configure custom per-key limits.

Plan Availability

Auth Endpoints

Register

string
required
Full name of the user
string
required
Email address
string
required
Password (min 8 chars, must include uppercase, lowercase, and digit)
string
IANA timezone string (e.g., “America/New_York”)
string
Optional invitation token to join an organization

Sign Out

Forgot Password

Reset Password

Change Password (Authenticated)

Verify Email

Resend Verification Email

Permissions

API access respects your organization role:

Security

  • Account lockout after 5 failed login attempts (15-minute lockout, 30-minute reset)
  • Rate limiting on auth endpoints to prevent brute force
  • Passwords hashed with bcryptjs
  • API keys encrypted at rest with AES-256-GCM

Share Token Authentication

Some endpoints support unauthenticated access via share tokens for external collaboration:
Supported on: project detail, PRD content, status history, and activity endpoints.