Troubleshooting
Error codes the Pentify Terminal surfaces, and the fastest way to recover from each.
not_paired_yet (HTTP 404)
The pairing page hasn’t been completed yet. The Terminal polls for up to 5 minutes after pentify login. If polling timed out, re-run pentify login and authorize the device in the browser tab.
pairing_consumed (HTTP 410)
Your pairing was already redeemed by another process. This usually means a parallel pentify login ran. Re-run pentify login to start a fresh pairing.
invalid_api_key (HTTP 401)
The token is missing, malformed, or revoked. Run pentify status to inspect what the Terminal is sending, then pentify login to re-pair.
insufficient_tokens (HTTP 402)
Your workspace token balance is below the requested operation cost. Visit the URL printed in details.top_up_url to buy a token pack, or see Tokens & pricing.
insufficient_scope (HTTP 403)
The token lacks a required scope. Re-pair with pentify login to mint a fresh full-scope token, or open Settings → API keys to widen scopes on the existing key.
target_not_verified (HTTP 409)
The API refuses to scan unverified hostnames. Run:
pentify targets verify <hostname>Follow the printed DNS TXT or /.well-known instructions, then retry the scan.
rate_limited (HTTP 429)
The default rate limit is 60 requests per minute per key. Wait the seconds shown in the Retry-After response header. See Rate limits for details and headroom upgrades.
pairing timed out (client-side)
The Terminal didn’t see the browser tab complete authorization within 5 minutes. Common causes: the browser tab failed to open, you closed it before clicking Authorize this device, or the host is offline. Re-run pentify login; copy-paste the printed pairing URL into a browser if auto-open failed.