Skip to content

Authentication Errors

Outcome: Fix signup/login failures and expired-session errors. Audience: Everyone · Tags: troubleshooting, auth, login, signup

This page covers signing in to SnapLink itself — creating an account, logging in, and staying logged in.

Looking for a connector that shows an auth error on a run (Slack, HubSpot, Email, REST, …)? That's a different kind of "auth" — a connector credential, not your SnapLink login. See Connector failed instead.

Symptoms → cause → fix

"A valid email is required" (INVALID_EMAIL, 400)

The email you typed on sign-up doesn't look like an email address (it needs an @). Fix: re-check for typos and try again.

"Password must be at least 8 characters" (WEAK_PASSWORD, 400)

Sign-up requires a password of 8 characters or more. There's no other complexity rule today. Fix: choose a longer password and try again.

"An account with this email already exists" (EMAIL_TAKEN, 409)

You (or someone) already signed up with this email. Fix: go to Log in instead of Sign up. If you don't remember creating an account, this is still the right move — retry login, since password reset flows depend on what your instance has enabled.

"Invalid email or password" (INVALID_CREDENTIALS, 401)

The email/password pair didn't match on login. SnapLink deliberately doesn't say which one was wrong (so no one can use the error to guess whether an email is registered). Fix: - Double-check for typos, especially trailing spaces and caps-lock. - Confirm you're using Log in, not accidentally re-submitting Sign up. - If you're sure the password is right, it may have been changed elsewhere, or the account may not exist yet — try Sign up.

"Missing bearer token" / session errors (UNAUTHENTICATED, 401)

Every API request needs a valid session token in an Authorization: Bearer <token> header. You'll see this as a sudden "please log in again" in the app, or as a raw 401 if you're calling the API directly. Causes, most likely first: 1. You're logged out or never completed login — log in again. 2. Your session token expired. Tokens are valid for a limited time (7 days by default); past that, the token fails with a message like "Token expired." Fix: log in again — the app will normally do this automatically and send you back to where you were. 3. The token is malformed or was tampered with (rare — usually a developer/integration bug). Fix: discard it and log in again to get a fresh one. 4. The whole API is unreachable/misconfigured, not just your session — if every request fails immediately, including a fresh login attempt, that's a server-side configuration issue, not something you can fix as a user. Contact your administrator.

Resolution steps

  1. Identify which message/code you saw above.
  2. Follow that entry's fix.
  3. If it's a login/session issue, log in again from the SnapLink app.
  4. If it's a developer/API workflow, re-request a token:
curl -s -X POST https://api.snaplink.cloudsolutionaccelerators.com/api/v1/auth/login \
  -H "Content-Type: application/json" \
  -d '{"email":"you@example.com","password":"your-password"}'

A healthy response looks like { "ok": true, "data": { "token": "...", "user": { ... } } }. An error looks like { "ok": false, "error": { "code": "INVALID_CREDENTIALS", "message": "..." } } — the code field is exactly the code named above.

  1. Confirm the session is valid:
curl -s https://api.snaplink.cloudsolutionaccelerators.com/api/v1/auth/session \
  -H "Authorization: Bearer $TOKEN"

Advanced diagnostics

  • Session tokens are self-issued by the SnapLink backend at login/signup — there's no separate identity provider to check.
  • A token's expiry is fixed at issue time; there is no "keep me logged in forever" mode today.
  • Developers: if every authenticated call fails with a 500 AUTH_NOT_CONFIGURED error (not 401), that's an operator-side misconfiguration (a missing signing secret), not a user credential problem — see Administration.

When to contact support

If INVALID_CREDENTIALS persists after a password you're confident is correct, or if you're stuck in a login loop (login appears to succeed but you're immediately signed out again). Include the email you're signing in with (never your password) and roughly when it started.

Related: Connector failed · Missing permissions · API Reference

Was this helpful? 👍 👎