---
title: "Add a GitHub organisation through your own GitHub login"
method: POST
path: "/client/github/add-installation"
tags: ["Apps"]
---

# Add a GitHub organisation through your own GitHub login

`POST /client/github/add-installation`

## Request

- Base URL: `https://api.roar-ai.com`
- URL: `https://api.roar-ai.com/client/github/add-installation`
- Auth: HTTP bearer

Body `{ installationId }`, taken from `/github/reachable`. Allowed while other workspaces use the installation and while this workspace already has connections. Re-checks with GitHub, using the caller’s own token, that they can reach it; one they cannot gets the same 404 as one that does not exist. Recorded as a person’s reach and never as company property — in particular an API key does not read through it, and every deploy is still checked against the person’s own GitHub access — even when the caller is an owner. Idempotent. Same policy as members connecting an account: an owner always, a member while the workspace allows it. A signed-in person; an API key is refused.

## Request body

- object
  - `installationId` string, required

## Response `200`

The account now on this workspace, whether it was already, and whether the workspace’s organisation limit allows it. (Response shape not yet modelled in this spec.)

- object

## Other responses

- `400`: The caller has not linked their own GitHub, or GitHub could not be asked
- `403`: Not allowed to connect here, or called with an API key
- `404`: No GitHub organisation to add

---

[API](https://skmtc.dev/roar-ai/apis/roar-ai-api.md) · [All operations](https://skmtc.dev/roar-ai/apis/roar-ai-api/llms.txt) · [OpenAPI document](https://skmtc.dev/roar-ai/apis/roar-ai-api/revisions/37e4d0d5a7fe?raw)