Accept an invite
Uses up the invite token. Without a session it creates the account (password required) and signs in. With a session whose email matches it adds the invite's grants to that account.
Needs no sign-in. Not available to MCP clients or the assistant.
application/json- body
token*stringThe token from the invite link.
1 <= length <= 200name?stringlength <= 80password?stringAt least 10 characters.
10 <= length <= 1024Success.
application/json- response
status*string|stringviewer*challenge?curl -X POST 'https://example.com/api/v1/invites.accept' \ -H 'Content-Type: application/json' \ -d '{ "token": "string"}'{ "status": "signedIn", "viewer": { "id": "string", "email": "[email protected]", "name": "string", "role": "owner" }, "challenge": { "ticket": "string", "methods": [ "totp" ], "expiresAt": "2019-08-24T14:15:22Z" }}Refresh GitHub App installations POST
Reads the App's installations from GitHub again, for when a webhook about a new or removed installation was missed. Needs `github.manage`, which owners and admins hold. Available to MCP clients and the assistant.
Invite someone POST
Creates an invite link for an email, as an admin or as a member with grants on projects and services. The link is returned once; send it yourself, or it is emailed when the panel has an SMTP channel. An admin invite from a browser session needs a sign-in or auth.reauth from the last 15 minutes (FORBIDDEN details.reason "reauth" otherwise); API keys need none. Needs `users.invite`, which owners and admins hold. Not available to MCP clients or the assistant.