---
title: "Transfer account ownership"
method: PATCH
path: "/accounts/{account}/owner"
tags: ["Account"]
---

# Transfer account ownership

`PATCH /accounts/{account}/owner`

## Request

- Base URL: `https://api.factuarea.com/v1`
- URL: `https://api.factuarea.com/v1/accounts/{account}/owner`
- Auth: one of:
  - HTTP bearer
  - API key in header `X-API-Key`

Put the account in the name of another member: the outgoing owner becomes `admin`, the target `owner`. Irreversible.
- Needs the `account:owner` scope, the current owner, and `Idempotency-Key`.
- `owner_user_id` is the person UUID, not the member `id`; 403 `owner_transfer_forbidden` if not the owner.
- 422 `business_rule_violation` for an invalid target. Requires the `account:owner` scope, which `*` does not cover: the API key must list it explicitly.

## Path parameters

- `account` string, uuid, required

## Headers

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

## Request body

- TransferAccountOwnershipV1Request
  - `owner_user_id` string, uuid, required: Public identifier (UUID v7) of the person who becomes the account owner.

## Response `200`

- object
  - `data` AccountOwner, required: The ownership of an account after a transfer. It carries NO `id` and that is not an omission: its identity is `account_id`, because the subject of the resource is the ownership of the account and not an entity of its own.
    - `account_id` string, uuid, required: Opaque identifier (UUID v7) of the account.
    - `object` 'account_owner', required: Always `account_owner`.
    - `owner_user_id` string, uuid, required: Opaque identifier (UUID v7) of the person who now owns the account.
    - `previous_owner_user_id` string, uuid, required: Opaque identifier (UUID v7) of the person who owned it before.

## 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. `account_not_found`: the account in the path does not exist or is not the account of the API key.
- `422`: Validation failed — e.g. the API key plan limit was reached, or an invoice language outside the allowed catalog (`es`, `en`, `ca`). The `error.param` field identifies which input is invalid, if any. `idempotency_key_reused`: the `Idempotency-Key` was already used with a different body; send a new key or the same body. `invalid_param_format` on `Idempotency-Key`: the key must be 1 to 255 printable ASCII characters. `idempotency_key_required`: this operation requires the `Idempotency-Key` header; the message names the rejected operation.
- `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)