Look up a user_code's metadata for the authorize page
curl 'https://api.justcrawl.io/api/v1/cli-auth/info?user_code=ABCD-EFGH'Returns the hostname submitted on /cli-auth/start plus the code’s
expiry timestamp so the browser-side authorize page can render a
friendly “Authorize raj-laptop?” prompt and a countdown. Unauthenticated
— the user_code itself is the bearer that gates this lookup. The
endpoint returns 404 for unknown codes, 410 for codes that have already
been used or have expired; treat 410 as “ask the user to re-run
jc auth login.” Errors are structured JustcrawlError bodies (Phase
0.6 contract) so the dashboard’s authorize page can render code-aware
copy without parsing.
Parameters
Section titled “Parameters”Query Parameters
Section titled “Query Parameters”The XXXX-YYYY code the user pasted into the browser.
Responses
Section titled “Responses”Code metadata. Used by the dashboard authorize page to render the confirm dialog.
object
Sanitized hostname the CLI submitted on /start.
Examplegenerated
{ "hostname": "example", "expires_at": "2026-04-15T12:00:00Z"}Validation failed — request body or query is missing/invalid
object
Example
{ "error": "Missing or invalid \"url\" field"}Unknown user_code.
Code expired or already used.
Unexpected server error. Logs and PostHog $exception capture
object
Example
{ "error": "Something went wrong"}