API reference › Team › Roles and users
Resend a user's onboarding invite
POST /v1/users/{id}/resend-invite
- Scope
team:write- Roles
- admin, scheduler
Issues a new set-password link and invalidates the previous one. Limited to one resend per user per five minutes. An admin's invite can be resent only by another admin, and only until it is accepted (no password set and never signed in); super-admin accounts are never targets.
Parameters
Path parameters
| Name | Type | Description |
|---|---|---|
id required | string | Tenant user ID Example |
Every call also sends Authorization and X-Tenant-ID; see Getting started.
Example request
curl -X POST "https://api.fetchfido.ai/v1/users/{id}/resend-invite" \
-H "Authorization: Bearer $FIDO_API_KEY" \
-H "X-Tenant-ID: $FIDO_TENANT_ID"Try it
Responses
200 Invite resent
Invite resent
{
"success": true,
"message": "Invite resent.",
"data": {
"inviteState": "invited",
"inviteExpiresAt": "2026-01-15 09:00:00"
}
}Response fields (5)
| Field | Type | Description |
|---|---|---|
success | boolean | Example |
message | string | Example |
data | object | |
data.inviteState | string | Example |
data.inviteExpiresAt | string (date-time) | Example |
401 Not signed in
Missing, invalid or expired API key.
{
"success": false,
"message": "Invalid API key. Org and user tier keys must send an X-Tenant-ID header naming the organization the key was issued for.",
"errors": null,
"code": "API_KEY_MISSING"
}Response fields (4)
| Field | Type | Description |
|---|---|---|
success | boolean | Example |
message | string | Example |
errors | any or null | Null on this status. |
code | string | Machine-readable reason, for branching on in client code. One of: |
403 Not allowed
Invites cannot be resent for this type of account, or the caller may not resend to an admin
{
"success": false,
"message": "You don't have permission to access this endpoint. This API key is missing the 'team:write' scope.",
"errors": null,
"code": ""
}Response fields (4)
| Field | Type | Description |
|---|---|---|
success | boolean | Example |
message | string | Example |
errors | any or null | Null on this status. |
code | string | Always empty on this status. Example |
404 Not found
No account found for the provided user
{
"success": false,
"message": "No account found for the provided user.",
"errors": null,
"code": ""
}Response fields (4)
| Field | Type | Description |
|---|---|---|
success | boolean | Example |
message | string | Example |
errors | any or null | |
code | string | Example |
409 Conflict
Account has already set a password, or is an admin who has already signed in (including with SSO)
{
"success": false,
"message": "This account has already set a password.",
"errors": null,
"code": ""
}Response fields (4)
| Field | Type | Description |
|---|---|---|
success | boolean | Example |
message | string | Example |
errors | any or null | |
code | string | Example |
422 Validation failed
Account has no login of its own
{
"success": false,
"message": "This account has no login of its own.",
"errors": null,
"code": ""
}Response fields (4)
| Field | Type | Description |
|---|---|---|
success | boolean | Example |
message | string | Example |
errors | any or null | |
code | string | Example |
429 Too many requests
Resent too recently
{
"success": false,
"message": "You've exceeded this API key's rate limit of 120 requests per minute. Try again in 37 seconds.",
"errors": null,
"code": "RATE_LIMITED"
}Response fields (4)
| Field | Type | Description |
|---|---|---|
success | boolean | Example |
message | string | Example |
errors | any or null | Null on this status. |
code | string | Machine-readable reason, for branching on in client code. One of: |