FruxonDocs
ApiDevice authorization

Look up a pending grant by its short user code — the approval page's "what am I approving?" call.

Requires Firebase JWT but no tenant (the user hasn't picked one yet). Returns display metadata only: who's asking (client type/name) and the access level the client requested. This is the server-side truth the page renders — URL query parameters are only ever a hint. Also backs the GitHub-style manual path where the user types the code their terminal shows instead of following the full link.

GET
/v1/deviceAuthorizations/{userCode}:lookup

Authorization

Bearer
AuthorizationBearer <token>

JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.

In: header

Path Parameters

userCode*string

The short user code, as typed or carried in the URL (hyphens/case tolerated).

Response Body

curl -X GET "https://api.fruxon.com/v1/deviceAuthorizations/string:lookup"
{
  "userCode": "string",
  "clientType": "CLI",
  "clientName": "string",
  "requestedPreset": "string",
  "expiresAt": 0
}
{
  "type": "string",
  "title": "string",
  "status": 0,
  "detail": "string",
  "instance": "string",
  "property1": null,
  "property2": null
}
Empty
{
  "type": "string",
  "title": "string",
  "status": 0,
  "detail": "string",
  "instance": "string",
  "property1": null,
  "property2": null
}
{
  "type": "string",
  "title": "string",
  "status": 0,
  "detail": "string",
  "instance": "string",
  "property1": null,
  "property2": null
}