Check the GitHub owner sign-up
Polls the device flow. With status done it uses up the setup token, creates the owner from the GitHub account (primary verified email) and signs them in.
Needs no sign-in. Not available to MCP clients or the assistant.
application/json- body
token*stringThe t= value of the installer's setup link.
1 <= length <= 200ticket*string1 <= length <= 200Success.
application/json- response
status*string|string|string|string|stringintervalSeconds*integer1 <= valueviewer?curl -X POST 'https://example.com/api/v1/setup.githubPoll' \ -H 'Content-Type: application/json' \ -d '{ "token": "string", "ticket": "string"}'{ "status": "pending", "intervalSeconds": 1, "viewer": { "id": "string", "email": "[email protected]", "name": "string", "role": "owner" }}Finish first-run setup POST
Marks the setup wizard as done, so the web app stops offering it. Steps left out can be done later in settings. Needs `setup.finish`, which owners and admins hold. Not available to MCP clients or the assistant.
Start creating the owner with GitHub POST
Checks the setup token and starts the GitHub device flow (like gh auth login). Show userCode, open verificationUri, then call setup.githubPoll every intervalSeconds. Needs no sign-in. Not available to MCP clients or the assistant.