Developer docs
Resend a team invitation
Send a pending team invitation again when its delivery was not confirmed. An invitation already queued for delivery is refused, and invitations to one address are limited each hour. No seat changes. Only the account owner's API keys and connected apps can resend, while the plan includes team seats.
POST
https://uetr.ai/api/v1/team/members/{member_id}/resend- MCP tool:
resend_team_invitation - Access: a key or connection with read and write access
- Only the account owner's keys and connections
Parameters
| Name | In | Type | Required | Description |
|---|---|---|---|---|
member_id | path | string (uuid) | Yes | The teammate's seat id, from list_team_members. |
Response
| Field | Type | Required | Description |
|---|---|---|---|
member_id | string (uuid) | Yes | |
email | string | Yes | |
delivery | sent, unverified | Yes | sent: the invitation is queued for delivery. unverified: delivery could not be confirmed, so the invitation may not arrive; resend_team_invitation can try again. |
Example
curl -X POST "https://uetr.ai/api/v1/team/members/6f1c2b9e-3d4a-4e8f-9b7c-1a2d3e4f5a6b/resend" \ -H "Authorization: Bearer $UETR_API_KEY"
The answer:
{
"member_id": "6f1c2b9e-3d4a-4e8f-9b7c-1a2d3e4f5a6b",
"email": "new.colleague@example.com",
"delivery": "sent"
}Refusals
Besides the access refusals every call can meet, this call can answer:
read_only_credential(403): Read-only key or connection.machine_writes_disabled(503): Changes are switched off.request_too_large(413): Request too large.not_permitted(403): Not permitted.invitation_not_pending(409): Invitation no longer pending.invitation_queued(409): Invitation already queued.invitation_rate_limited(429): Too many invitations.invitation_check_failed(503): Invitation not checked.invitation_send_failed(503): Invitation not sent.invitation_not_sent(503): Invitation not sent.