Skip to content
justcrawl.io

auth_invalid

auth_invalid

Section titled “auth_invalid”

HTTP status: 401 Unauthorized

How to fix

Section titled “How to fix”
  1. Confirm the key isn't a typo. API keys start with sr_live_ and are 40+ characters. Re-paste from the dashboard at Settings → API Keys rather than typing.
  2. Check the dashboard to see if the key was revoked. If it's missing from the list at Settings → API Keys, generate a new one.
  3. If you're using the CLI, re-run jc auth login. Your locally stored key in ~/.jc/config.json may be stale.
  4. If you're using the MCP server, update the JUSTCRAWL_API_KEY env var in your claude_desktop_config.json (or equivalent) and restart the agent host.

What this means

Section titled “What this means”

You sent an Authorization header, but the value didn't match an active API key for any organization. Either the key is wrong, was revoked from the dashboard, or has been rotated since you last copied it.

Section titled “Related errors”
  • auth_missing — no Authorization header at all
  • auth_forbidden — credentials are valid, but you lack permission for this action
  • auth_org_mismatch — the resource belongs to a different organization

Still stuck?

Section titled “Still stuck?”

Contact support with your request_id (looks like req_01HF3JKB...). We'll trace the auth attempt in our logs.