---
title: "Retrieve an employee"
method: GET
path: "/companies/{company}/employees/{employee}"
tags: ["Employees"]
---

# Retrieve an employee

`GET /companies/{company}/employees/{employee}`

## Request

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

Retrieve a single employee by its `id` (UUID v7). An employee belonging to another company returns 404 `employee_not_found` (anti-enumeration).

## Path parameters

- `company` string, uuid, required
- `employee` string, uuid, required

## Headers

- `Factuarea-Version` string, date

## Response `200`

- object
  - `data` Employee, required: An employee of your company. Active employees count towards the seat billing of the workforce module; deactivated ones are preserved with their termination date.
    - `id` string, uuid, required: Opaque identifier of the employee, a UUID v7 (e.g. `01931b3e-7c4a-7f2e-9a8b-3c5d6e7f8a9b`).
    - `object` 'employee', required: Always `employee`.
    - `first_name` string, required: Given name of the employee.
    - `last_name` string, required: Family name of the employee.
    - `email` string, email, required: Contact email of the employee.
    - `tax_id` string, nullable, required: Spanish fiscal identifier (NIF/NIE) of the employee, or `null` when unknown. Not a foreign key.
    - `job_title` string, nullable, required: Role or position of the employee, or `null` when unset.
    - `employment_type` 'full_time' | 'part_time', required: Working-hours arrangement: `full_time` or `part_time`.
    - `contract_hours` number, float, required: Weekly contracted hours (e.g. `40` for a full-time schedule).
    - `hire_date` string, date, required: Calendar date the employee was hired, in `Y-m-d`.
    - `termination_date` string, date, nullable, required: Calendar date the employee was deactivated, in `Y-m-d`; `null` while active.
    - `ccaa` 'AN' | 'AR' | 'AS' | 'IB' | 'CN' | 'CB' | 'CL' | 'CM' | 'CT' | 'VC' | 'EX' | 'GA' | 'MD' | 'MC' | 'NC' | 'PV' | 'RI' | 'CE' | 'ML', required: Spanish autonomous community (comunidad autónoma) the employee is assigned to, as its two-letter code.
    - `status` 'active' | 'inactive', required: Lifecycle status: `active` (in the workforce) or `inactive` (deactivated).
    - `external_id` string, nullable: External integration key (ERP/CRM/HR system) mapping this employee to a record in a third-party system. Free-format, unique per company, distinct from the fiscal `tax_id`.
    - `metadata` Metadata, nullable, required: A free map of up to 50 key→value pairs for storing arbitrary structured data (values are strings up to 500 characters). Unlike `custom_fields` — an ordered list of typed `{field, value}` pairs with display semantics, present on the six document resources — `metadata` is an unordered map for opaque integration data; a document may carry both. The master resources (Client, Supplier) have no `custom_fields`, so their `metadata` doubles as the custom-fields store. **Reserved keys (read-only).** When the system auto-issues an invoice from a payment correlation (Stripe/GoCardless/MONEI), it writes `stripe_subscription_id`, `stripe_invoice_id`, `billing_reason`, `period_start` and `period_end` into that invoice metadata automatically. Do not set or overwrite them by hand — the platform owns them and a manual value may be replaced when the correlation runs.
    - `user_id` string, uuid, nullable, required: UUID v7 of the portal user linked to this employee, or `null` when no linkage exists yet.
    - `created_at` string, date-time, nullable, required: Creation timestamp (ISO 8601).
    - `updated_at` string, date-time, nullable, required: Last-update 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.
- `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)