Change a repository's visibility
Make a repository public or private.
/repos/{owner}/{name}/visibilityNeeds the Admin role, and confirm must be its full name, owner/name. Making it public shows it, its code, issues and pull requests to everyone and adds it to search for everyone. Making it private hides it from everyone without a role on it; a free workspace takes it only while its private storage has room. Nothing else about it changes.
Needs the Admin role (403 otherwise). Refused with 422 when confirm is not the repository’s full name, and with 402 when a free workspace’s private storage has no room for it. See Change who can see a repository.
- Authentication: Required. Send an access token as
Authorization: Bearer. - MCP tool:
set_repo_visibility, with the same inputs
Path parameters
Section titled “Path parameters”| Name | Type | Required | Description |
|---|---|---|---|
owner |
string | Yes | The workspace that owns the repository. |
name |
string | Yes | The repository’s name. |
Body parameters
Section titled “Body parameters”Send a JSON object. Names are snake_case, as in responses; the camelCase spelling is accepted too.
| Name | Type | Required | Description |
|---|---|---|---|
private |
boolean | Yes | true to make it private, false to make it public. |
confirm |
string | Yes | Its full name, owner/name, typed out, to confirm. |
Example request
Section titled “Example request”curl -X POST https://api.g1t.sh/repos/flagon-io/hello/visibility \ -H "Authorization: Bearer $G1T_TOKEN" \ -H "Content-Type: application/json" \ -d '{ "private": true, "confirm": "flagon-io/hello" }'Example response
Section titled “Example response”A successful request answers 200 with:
{ "id": "rep_01m3m5q6p0e2qaw6mmjahk0qrr", "namespace": "flagon-io", "name": "hello", "description": "A tiny service that says hello.", "is_private": true, "owner_id": "usr_01kkntcg1eeb98j62xjm7eh09p", "default_branch": "main", "fork_of": null, "protected": true, "created_at": "2026-09-28T14:11:52.640Z", "topics": [ "http", "example" ], "website": "https://hello.g1t.page", "archived_at": null}Errors
Section titled “Errors”A failed request answers with one of these statuses and a body like {"error": {"code": "not_found", "message": "Repository not found."}}. See errors.
| Status | Code | When |
|---|---|---|
| 401 | unauthenticated |
A token is required, or the one sent is not valid. |
| 402 | payment_required |
The workspace cannot start this work: it needs the g1t plan or a card check, or it is at a limit. See usage and billing. |
| 403 | forbidden |
The token is valid but not allowed to do this, such as a member-only change or an agent token outside its repository. |
| 404 | not_found |
It does not exist, or you cannot see it. |
| 409 | conflict |
The request conflicts with the current state. |
| 422 | invalid |
The input is not valid. message says which field and why. |