> For the complete documentation index, see [llms.txt](https://tri.gitbook.io/tri-doc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tri.gitbook.io/tri-doc/liquidity-pool/edit-employee.md).

# Edit Employee

### Liquidity Pool

<mark style="color:blue;">`PATCH`</mark> <https://sandbox.triangle.digital/api/v2/liquidity\\_pool/clients/{client\\_id}/employees/{employee\\_id}>

Changes the details of an employee of the client. Send only the fields to change: a field left out keeps its stored value, a field sent empty is cleared. At least one of the fields below has to be sent.

The employee's company cannot be changed here, and an Individual Consumption cannot be edited through this call — it is addressed by its own uuid and answers `Employee not found for this client.`

All validation problems are returned at once in `data.errors`. The answer carries the employee as [Get Employees](/tri-doc/liquidity-pool/get-employees.md) returns it.

**Path parameters**

<table data-full-width="true" data-search="false"><thead><tr><th width="230">Name</th><th width="110">Type</th><th>Description</th><th width="210">Where to take it from</th></tr></thead><tbody><tr><td><code>client_id</code></td><td>integer</td><td><strong>Required.</strong> The client the employee belongs to.</td><td><a href="/tri-doc/liquidity-pool/get-clients.md">Get Clients</a> — <code>client_id</code></td></tr><tr><td><code>employee_id</code></td><td>integer</td><td><strong>Required.</strong> The employee to change.</td><td><a href="/tri-doc/liquidity-pool/get-employees.md">Get Employees</a> — <code>employee_id</code></td></tr></tbody></table>

**Headers**

<table data-full-width="true"><thead><tr><th>Name</th><th>Value</th></tr></thead><tbody><tr><td>Content-Type</td><td><code>application/json</code></td></tr></tbody></table>

**Body**

<table data-full-width="true" data-search="false"><thead><tr><th width="200">Name</th><th width="110">Type</th><th>Description</th><th width="260">Example</th></tr></thead><tbody><tr><td><code>hash</code></td><td>string</td><td><strong>Required.</strong> API key.</td><td>fk5f0iuy-rr06-j4x3-i75b-fy2s67s4ilo1</td></tr><tr><td><code>employee_name</code></td><td>string</td><td>Employee name. Cannot be cleared — sending it empty is refused.</td><td>John Smith</td></tr><tr><td><code>employee_number</code></td><td>string</td><td>Client-facing Employee ID — the client assigns the value, as used in its own systems. Unique within the client when given.</td><td>D2354324</td></tr><tr><td><code>country</code></td><td>string</td><td>Country.</td><td>United States</td></tr><tr><td><code>address</code></td><td>string</td><td>Address line 1.</td><td>6700 Woodlands Pkwy</td></tr><tr><td><code>address_2</code></td><td>string</td><td>Address line 2.</td><td>Suite 230</td></tr><tr><td><code>city</code></td><td>string</td><td>City.</td><td>The Woodlands</td></tr><tr><td><code>state</code></td><td>string</td><td>State.</td><td>NY</td></tr><tr><td><code>zip</code></td><td>string</td><td>Zip code.</td><td>77382</td></tr></tbody></table>

```json
{
    "hash": "fk5f0iuy-rr06-j4x3-i75b-fy2s67s4ilo1",
    "employee_name": "John Smith",
    "address": "6700 Woodlands Pkwy",
    "address_2": "Suite 230"
}
```

**Response fields**

<table data-full-width="true" data-search="false"><thead><tr><th width="300">Field</th><th width="110">Type</th><th>Description</th></tr></thead><tbody><tr><td><code>message</code></td><td>string</td><td>Human-readable result of the call.</td></tr><tr><td><code>success</code></td><td>boolean</td><td>Whether the employee was updated; a refused call answers HTTP 400.</td></tr><tr><td><code>data.employee_id</code></td><td>integer</td><td>The employee, as in <a href="/tri-doc/liquidity-pool/get-employees.md">Get Employees</a> — <code>employee_id</code>.</td></tr><tr><td><code>data.employee_number</code> / <code>employee_name</code></td><td>string</td><td>The stored values after the change.</td></tr><tr><td><code>data.company_id</code></td><td>uuid</td><td>Company of the employee, as in <a href="/tri-doc/liquidity-pool/get-companies.md">Get Companies</a>; empty when none. Not changed by this call.</td></tr><tr><td><code>data.country</code> / <code>address</code> / <code>address_2</code> / <code>state</code> / <code>city</code> / <code>zip</code></td><td>string</td><td>The stored address after the change.</td></tr><tr><td><code>data.credit_card</code></td><td>boolean</td><td>Whether a card is attached.</td></tr><tr><td><code>data.master_card</code></td><td>boolean</td><td>Whether a MasterCard card is attached.</td></tr><tr><td><code>data.last_pay_error</code></td><td>boolean</td><td>Whether the last payment failed.</td></tr><tr><td><code>data.last_pay_at</code></td><td>string</td><td>When the last payment happened, MM/DD/YYYY HH:MM:SS UTC +00:00; empty when there was none.</td></tr><tr><td><code>data.errors</code></td><td>array</td><td>400 only — every validation problem, one per entry.</td></tr><tr><td><code>operations_count</code></td><td>integer</td><td>Always <code>1</code>.</td></tr></tbody></table>

**Response**

{% tabs %}
{% tab title="200" %}
{% code fullWidth="false" %}

```json
{
    "message": "Employee updated successfully.",
    "success": true,
    "data": {
        "employee_id": 18,
        "employee_number": "D2354324",
        "employee_name": "John Smith",
        "company_id": "68117898-4278-499f-b96b-78173f3d2040",
        "country": "United States",
        "address": "6700 Woodlands Pkwy",
        "address_2": "Suite 230",
        "city": "The Woodlands",
        "state": "NY",
        "zip": "77382",
        "credit_card": true,
        "master_card": false,
        "last_pay_error": false,
        "last_pay_at": "08/05/2026 11:46:50 UTC +00:00"
    },
    "operations_count": 1
}
```

{% endcode %}
{% endtab %}

{% tab title="400" %}
Nothing was changed. A field that is not valid comes back in `data.errors` — every problem at once. The other refusals answer with an empty `data`: `Employee not found for this client.` — the employee is unknown, belongs to another client, or is an Individual Consumption; `Nothing to update. Send at least one of: employee_name, employee_number, country, address, address_2, city, state, zip.`

```json
{
    "message": "Employee Name is required. Employee ID already exists",
    "success": false,
    "data": {
        "errors": [
            "Employee Name is required",
            "Employee ID already exists"
        ]
    },
    "operations_count": 1
}
```

{% endtab %}
{% endtabs %}