Skip to Content
SeyloDocs
API referenceGitHub

Check the GitHub device flow

POST
/api/v1/github.devicePoll

Checks whether the person entered the code on GitHub. Once done, the token is stored sealed as a git credential for github.com and the login is returned. A mutation because finishing it stores the credential.

Needs github.manage, which owners and admins hold. Not available to MCP clients or the assistant.

Authorization

cookieseylo_session<token>

Request Body

application/json
  1. body
flowId*string

Panel-issued id.

Match^[a-z0-9]{16}$

Response Body

Success.

application/json
  1. response
status*string|string|string|string
login*string|null
gitCredentialId*|null
Example Request
curl -X POST 'https://example.com/api/v1/github.devicePoll' \  -H 'Content-Type: application/json' \  -d '{  "flowId": "string"}'
Example Response
{  "status": "pending",  "login": "string",  "gitCredentialId": "string"}

Disconnect the GitHub account POST

Deletes the device-flow token used for private repos. Services that clone with it fail to deploy until they get another credential. Revoke it on github.com too. Needs `github.manage`, which owners and admins hold. Not available to MCP clients or the assistant.

Connect a GitHub account for private repos POST

Starts the GitHub device flow (like gh auth login) to get a token with the repo scope, so the panel can clone private repositories without the App. Show userCode and open verificationUri, then poll github.devicePoll every intervalSeconds. Opt-in; the App stays the recommended way. Needs `github.manage`, which owners and admins hold. Not available to MCP clients or the assistant.