

Authentication in TaskForge is built on industry-standard OAuth 2.0 and API key-based mechanisms, giving you flexible options depending on your integration needs. Every request to the TaskForge API must be authenticated — unauthenticated requests will return a <401 Unauthorized> response.
This guide walks you through the two primary authentication methods, how to manage credentials, and best practices for keeping your account secure.
API keys are the simplest way to authenticate requests to the TaskForge API. Each workspace generates a unique API key that you include in the request header.
To generate your API key:
API keys can be scoped to specific permissions (read-only, write, admin) and can be revoked at any time from the Settings panel.
For applications that act on behalf of users, TaskForge supports the OAuth 2.0 Authorization Code flow. This is the recommended approach for third-party integrations and multi-user applications.
The flow works as follows:
client_id> and requested <scopes>.redirect_uri> with an authorization code.client_secret>.
Access tokens expire after 1 hour. Use the refresh token to obtain a new access token without requiring the user to re-authenticate.
TaskForge issues both short-lived access tokens and long-lived refresh tokens. You should store refresh tokens securely and never expose them in client-side code or version control systems.
To rotate a compromised token:
Two-factor authentication (2FA) adds an additional layer of protection to your TaskForge account. Once enabled, you will be prompted to enter a one-time code from your authenticator app each time you sign in. To enable 2FA:
If you encounter authentication errors, here are the most common causes and how to resolve them: