Authentication Both

The TapTidy API supports two credential types for programmatic and third-party access: Personal Access Tokens (PATs) and App Passwords. Both require a TapTidy Pro subscription and are generated under Settings → Developer.

Personal Access Tokens (Bearer Auth)

Send your token as an HTTP Bearer credential in the Authorization header:

Authorization: Bearer taptidy_pat_<id>.<secret>

Personal access tokens are the recommended credential for scripts, CLI utilities, and unattended integrations such as Home Assistant. The prefix allows indexed server lookup. If an account is deactivated, all associated tokens are revoked immediately.

App Passwords (HTTP Basic Auth)

Send your account email and app password via HTTP Basic authentication:

Authorization: Basic base64(email:<app-password-id>.<secret>)

App passwords provide compatibility for clients expecting standard Basic Auth (such as CalDAV sync clients, Obsidian plugins, or command-line scripts).

Token Scopes & Granularity

Both token types enforce strict least-privilege scoping:

• tasks:read, tasks:write
• routines:read, routines:write
• household:read, household:write

A request lacking the necessary scope will receive an insufficient_scope error (see API Errors).