Skip to Content
SeyloDocs
API referenceSign-in and account

Start linking your GitHub login

POST
/api/v1/auth.githubLinkStart

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.

Authorization

cookieseylo_session<token>

Request Body

application/json
  1. body
repoAccess*boolean

Also ask for the repo scope so this GitHub login can clone private repos. Off by default: a GitHub App gives narrower access.

Defaultfalse

Response Body

Success.

application/json
  1. response
ticket*string
userCode*string
verificationUri*string
expiresAt*string
Formatdate-time
intervalSeconds*integer
Range1 <= value
Example Request
curl -X POST 'https://example.com/api/v1/auth.githubLinkStart' \  -H 'Content-Type: application/json' \  -d '{  "repoAccess": false}'
Example Response
{  "ticket": "string",  "userCode": "string",  "verificationUri": "string",  "expiresAt": "2019-08-24T14:15:22Z",  "intervalSeconds": 1}

Check a GitHub link POST

Polls the device flow started by auth.githubLinkStart. With status done the GitHub login is linked. CONFLICT when that login belongs to someone else. Any signed-in caller. Not available to MCP clients or the assistant.

Check a GitHub sign-in POST

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.