CLI

Errors

What each failure means and what to do about it.

StatusMeaningWhat to do
400A required parameter is missingOften a locationId — pin one with pxb location use
401The token was rejectedDisconnected or revoked; run pxb auth again
403Missing a scopeGrant it under Dev Tools → CLI, or to the API client
404No such record, or no such endpointCheck the path; pxb help commands lists the forms
429Rate limitedThe message says how long to wait

Local failures worth naming:

  • "This sign-in has ended" — it was disconnected under Dev Tools → CLI, a refresh token was used twice, or it sat unused for 90 days. Run pxb auth.
  • "Sign-in was cancelled in the browser" — you chose Cancel on the consent page. Nothing was connected.
  • "Sign-in was declined in the browser" — the same, for --device.
  • "The sign-in code expired" — nobody approved pxb auth --device within 30 minutes. Run it again for a new code.
  • "No stored client secret" — the keychain entry is gone. Run pxb auth; your client ID is remembered, so you only need the secret.
  • "Could not read the client secret" — the keychain is locked or unavailable. Unlock it and run the same command again; nothing was lost.
  • "Refusing to send credentials" — --base-url (or PXB_BASE_URL) is plain http on a host other than localhost. Use its https address.

In your terminal: pxb help errors