GitHub Authorization Failed

github-authorization-failed · 400

GitHub refused to finish the sign-in the connect flow started, so nothing was linked.

reason is GitHub's own error code, or no-access-token. It is a 400, not a 401, so the console keeps the user signed in to Ghaym.

Besides the members every error carries, this type adds reason.

Common causes

  • The code GitHub sent back was already used, or had expired.
  • The flow was finished from an old or reloaded tab.
  • The deployment's GitHub App settings don't match the address GitHub returned to.

How to fix the call

  • Start the connect flow again from the console, or with ghaym cloud git install, and finish it in one go.
  • This one needs the user: an agent can't finish a GitHub sign-in alone.

Example response

json
{
  "type": "github-authorization-failed",
  "title": "GitHub Authorization Failed",
  "detail": "GitHub did not complete the authorization. Start the connect flow again.",
  "reason": "bad_verification_code",
  "requestId": "req-1785231000000-4f7b2c9ae",
  "timestamp": "2026-07-28T09:30:00.000Z",
  "path": "/v1/git/installations/connect",
  "method": "POST",
  "instance": "POST /v1/git/installations/connect",
  "status": 400,
  "docs": "https://ghaym.me/docs/errors/github-authorization-failed"
}