List your repository invitations
The invitations to repositories waiting for you to answer, sent to your username or to one of your confirmed email addresses, newest first.
GET
/user/repository_invitationsAccept or decline each by its id. People only; an agent’s or a workspace’s token gets an empty list.
Invitations sent to your username, and to any of your confirmed addresses before you had an account, newest first. Accept one with PATCH /user/repository_invitations/{id}, or decline it with DELETE. Expired and answered ones are left out.
- Authentication: Required. Send an access token as
Authorization: Bearer. - MCP tool:
list_my_repo_invitations, with the same inputs
Example request
Section titled “Example request”curl https://api.g1t.sh/user/repository_invitations \ -H "Authorization: Bearer $G1T_TOKEN"Example response
Section titled “Example response”A successful request answers 200 with:
[ { "id": "rin_01kp3e9f0g1h2j3k4m5n6p7q8r", "repo": "flagon-io/hello", "repo_id": "rep_01m3m5q6p0e2qaw6mmjahk0qrr", "invitee": "ada", "email": null, "role": "triage", "invited_by": "syntaqx", "inviter_avatar": null, "status": "pending", "created_at": "2026-10-05T17:00:00.000Z", "expires_at": "2026-10-12T17:00:00.000Z" }]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. |
| 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. |
| 422 | invalid |
The input is not valid. message says which field and why. |