Invites

Send an invite to g1t again

Send a pending invite to g1t again: the same email, with the same link, to the same address.

POST/user/invites/{id}/resend

Refused with 409 when it is no longer pending.

Sends the same email again, with the same link; when it stops working does not change. Refused with 409 unless it is pending.

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

Path parameters

Name	Type	Required	Description
`id`	string	Yes	The invite’s id, such as inv_01k…

Example request

curl -X POST https://api.g1t.sh/user/invites/id/resend \
  -H "Authorization: Bearer $G1T_TOKEN"

Example response

A successful request answers 200 with:

{
  "id": "inv_01kp2x7m8n9q0r1s2t3v4w5x6y",
  "code": "g1t-k7m2-q9xd-4hpw-…",
  "hint": "g1t-k7m2",
  "email": "ada@example.com",
  "kind": "account",
  "workspace": null,
  "status": "pending",
  "charged_to": "user",
  "invited_by": "syntaqx",
  "redeemed_by": null,
  "created_at": "2026-10-05T17:00:00.000Z",
  "expires_at": "2026-11-04T17:00:00.000Z",
  "redeemed_at": null,
  "revoked_at": null,
  "invitee": null,
  "role": null
}

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 a token without the scope it needs.
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.