Documentation Index
Fetch the complete documentation index at: https://docs.linkutm.com/llms.txt
Use this file to discover all available pages before exploring further.
Overview
All API endpoints authenticate with a JWT bearer token. Tokens are issued by signup (OTP verification), login, or Google OAuth, and carried on every request:/api/v1/auth and do not require the x-workspace-id header.
Signup (OTP flow)
Account creation is a two-step flow: request an OTP, then verify it.Step 1: Send OTP
Email address for the new account.
Display name.
Account password. Minimum 8 characters.
Step 2: Verify OTP
Same email used in
send-otp.The code from the email. Minimum 6 characters.
Resend OTP
Email to resend the code to. Use when the original code expired or was not received.
Login
Account email.
Account password.
verify-otp.
Password management
Forgot password
Email to send a password-reset link to.
Reset password
Reset token from the email link.
New password. Minimum 8 characters.
Change password
The current password, for verification.
New password. Minimum 8 characters.
Profile
Sessions
Each sign-in creates a session record. Theuser-agent header on the request is captured so users can identify devices.
List sessions
Revoke one session
Revoke all sessions
Google OAuth
GET /auth/google to start the Google OAuth flow. After Google authenticates the user, the callback redirects to:
token query parameter from that redirect and use it as the bearer token.
The Google OAuth endpoints are browser-redirect endpoints, not JSON APIs. Do not call them with
fetch/curl expecting a JSON body.Errors
| Code | When |
|---|---|
400 | Validation failure - missing fields, password too short, invalid OTP |
401 | Wrong credentials, expired or invalid JWT, expired reset token |
409 | Email already registered |
429 | Rate limit exceeded (100 requests/minute per IP) |