List your workspace invitations

The invitations to workspaces waiting for your answer, newest first: each one's id, the workspace (slug, name, avatar), the role accepting gives (member or owner), who sent it (invited_by, null when g1t staff did), and when it was made and when it expires.

GET/user/invitations

Expired, revoked and answered ones are left out. Accept or decline each by its id. People only; an agent’s or a workspace’s token gets an empty list.

Accept one with POST /user/invitations/{id}/accept, or decline it with POST /user/invitations/{id}/decline. An agent’s or a workspace’s token gets an empty list.

Authentication: Required. Send an access token as Authorization: Bearer.
MCP tool: account with action list_workspace_invitations, and the same inputs
Scope: An access token needs account:read.

Example request

curl https://api.g1t.sh/user/invitations \
  -H "Authorization: Bearer $G1T_TOKEN"

Example response

A successful request answers 200 with:

[
  {
    "id": "inv_01kp2x7m8n9q0r1s2t3v4w5x6y",
    "workspace": {
      "slug": "acme-labs",
      "name": "Acme Labs",
      "avatar": null
    },
    "role": "member",
    "invited_by": {
      "username": "syntaqx",
      "display_username": "syntaqx",
      "name": "Chase",
      "avatar": null
    },
    "created_at": "2026-10-05T17:00:00.000Z",
    "expires_at": "2026-11-04T17:00:00.000Z"
  }
]

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.