---
title: "Resend an employee invitation"
method: POST
path: "/companies/{company}/employee-invitations/{invitation}/resend"
tags: ["Employees"]
---

# Resend an employee invitation

`POST /companies/{company}/employee-invitations/{invitation}/resend`

## Request

- Base URL: `https://api.factuarea.com/v1`
- URL: `https://api.factuarea.com/v1/companies/{company}/employee-invitations/{invitation}/resend`
- Auth: one of:
  - HTTP bearer
  - API key in header `X-API-Key`

Resend a pending employee invitation identified by its `id` (UUID v7), regenerating its token and expiry and re-sending the invitation email. Returns 422 if the invitation was already accepted or canceled, and 404 if it does not exist in your company.

## Path parameters

- `company` string, uuid, required
- `invitation` string, uuid, required

## Headers

- `Idempotency-Key` string, required
- `Factuarea-Version` string, date

## Response `200`

- object
  - `data` EmployeeInvitation, required: An invitation for a person to join your company as an employee (Control Horario portal). Reuses the invitation subsystem with role `employee`; it does not consume the plan `users` seat limit.
    - `id` string, uuid, required: Opaque identifier of the invitation, a UUID v7 (e.g. `01931b3e-7c4a-7f2e-9a8b-3c5d6e7f8a9b`).
    - `object` 'employee_invitation', required: Always `employee_invitation`.
    - `email` string, email, required: Email address the invitation was sent to.
    - `role` 'employee', required: Always `employee` for this surface.
    - `status` 'pending' | 'accepted' | 'canceled' | 'expired', required: Lifecycle status of the invitation: `pending` (awaiting acceptance), `accepted`, `canceled` or `expired`.
    - `expires_at` string, date-time, nullable, required: Expiry timestamp of the invitation link (ISO 8601), or `null`.
    - `created_at` string, date-time, nullable, required: Creation timestamp (ISO 8601).

## Other responses

- `400`: `parameter_unknown` with `subcode` `retired_active_profile_header`: the retired `X-Active-Profile` header was sent; the company goes in the path. `parameter_invalid_format` on `Factuarea-Version`: the header is not a `YYYY-MM-DD` date. `unsupported_api_version`: the `Factuarea-Version` date is not a supported version.
- `401`: Missing or invalid API key.
- `403`: The request is authenticated but not allowed: the API key lacks the required scope (`insufficient_scope`), the plan does not include the public API or this feature (`addon_not_active`, `feature_not_available_in_plan`), or the module is not available with a test key (`module_not_available_in_sandbox`).
- `404`: The requested resource does not exist or belongs to another company.
- `422`: Validation failed. The `error.param` field identifies which input is invalid.
- `429`: Rate limit exceeded. Retry after the duration in `Retry-After`.
- `500`: Unexpected server error.

---

[API](https://skmtc.dev/factuarea/apis/factuarea-public-api.md) · [All operations](https://skmtc.dev/factuarea/apis/factuarea-public-api/llms.txt) · [OpenAPI document](https://skmtc.dev/factuarea/apis/factuarea-public-api/revisions/718e77934422?raw)