Check a GitHub sign-in
Polls the device flow. With status done it signs in the person linked to that GitHub login (result holds the LoginResult); noAccount when nobody is linked to it.
Needs no sign-in. Not available to MCP clients or the assistant.
application/json- body
ticket*string1 <= length <= 200Success.
application/json- response
status*string|string|string|string|string|stringintervalSeconds*integer1 <= valueresult?curl -X POST 'https://example.com/api/v1/auth.githubPoll' \ -H 'Content-Type: application/json' \ -d '{ "ticket": "string"}'{ "status": "pending", "intervalSeconds": 1, "result": { "status": "signedIn", "viewer": { "id": "string", "email": "[email protected]", "name": "string", "role": "owner" }, "challenge": { "ticket": "string", "methods": [ "totp" ], "expiresAt": "2019-08-24T14:15:22Z" } }}Start linking your GitHub login POST
Starts the device flow to link a GitHub login to the signed-in person, so they can sign in with GitHub later. Needs a sign-in or auth.reauth from the last 15 minutes (FORBIDDEN details.reason "reauth" otherwise). Any signed-in caller. Not available to MCP clients or the assistant.
Start signing in with GitHub POST
Starts the GitHub device flow for sign-in. Show userCode, open verificationUri, then call auth.githubPoll every intervalSeconds. UNAVAILABLE while the OAuth client id is a placeholder. Needs no sign-in. Not available to MCP clients or the assistant.