# Bulk update allocations

Operation ID: `updateAllocations`

Group: PSA › Allocations

[Open in the interactive reference](https://docs.api.lensing.ai/lensing/v1/endpoints/updateAllocations)

`PATCH /psa/allocations`

Retry-safe: A write that accepts Idempotency-Key: repeating a request with the same key replays the stored answer instead of executing twice.

Updates multiple allocations in one request, with the fields you send. A field you leave out keeps its current value. To clear notes or workingDays, send null.

To reassign an allocation, send a new memberId. memberEmployeeId, memberPlaceholderId, and psaProjectId are ignored, and an allocation can't move to another project. Every update recalculates the allocation's daily entries from its dates, totalHours, method, and workingDays.

If any id matches no allocation, the request fails with NOT_FOUND and nothing is updated. The response is empty. Read an updated allocation with GET psa/allocations/:id.

## Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `Api-Version` | header | string · v1 | yes | The API version this request targets, named by its public identifier. Required on every request; omitting it, or naming a version this company does not have, is answered with 400. This document describes version `v1`. |
| `Idempotency-Key` | header | string | no | An opaque caller-chosen string (1-255 characters) that makes this request safe to retry. Repeating the same key with an identical request body replays the original response instead of re-executing - but only once that original request succeeded; a failed attempt re-executes on retry. Repeating the key with a different body is answered with 422. A key still in flight is answered with 409 - as is a key whose original request was interrupted before it finished, for a few minutes afterwards, until that attempt is presumed dead. A completed response stays replayable for 24 hours. The key is scoped to the caller, not to the action: reusing it for a different action is answered with 409 or 422 rather than treated independently. On read actions this header is ignored. On write actions that cannot offer the guarantee it is answered with `400 IDEMPOTENCY_NOT_SUPPORTED` rather than silently ignored. |

## Request body

Required, `application/json`: updateAllocationsInput.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `allocations` | array<object> | yes | The allocations to update. Example: `[{"id":"3f2a91c7-5d84-4b1e-9c60-8a7e2d4f0b13","totalHours":"32.00"},{"id":"b7c40e29-1af6-42d8-8e55-6d3b9c018a74","memberId":51204,"projectActivityId":8317,"startDate":"2026-09-01","endDate":"2026-11-30","totalHours":"160.00","method":"hoursPerWeek","notes":"Rescoped after the change order.","workingDays":["Monday","Tuesday","Wednesday","Thursday"],"memberEmployeeId":3889611,"psaProjectId":32341}]`. |
| `allocations[].id` | string | yes | The unique identifier of the allocation to update. The call is all-or-nothing: if any identifier matches no allocation, nothing is updated. |
| `allocations[].memberId` | number | no | A new timetracking member assignment to book the allocation against. It is a numeric key, not the UUID that GET psa/team-members/:id takes. |
| `allocations[].projectActivityId` | number | no | A new project activity for the allocation. It is a numeric key, not the UUID that GET psa/activities/:id takes. |
| `allocations[].startDate` | date | no | A new first day of the allocation period, inclusive. Use format YYYY-MM-DD. |
| `allocations[].endDate` | date | no | A new last day of the allocation period, inclusive. Use format YYYY-MM-DD. |
| `allocations[].totalHours` | decimal | no | New planned hours, interpreted according to method as on create. Changing this regenerates the allocation's daily entries. |
| `allocations[].method` | any | no | The distribution method for the planned hours. One of: `"totalHours"`, `"hoursPerDay"`, `"hoursPerWeek"`, `"hoursPerMonth"`. |
| `allocations[].notes` | string \| null | no | Free-form notes stored on the allocation. |
| `allocations[].workingDays` | array<any> \| null | no | The days of the week the allocation applies to. |
| `allocations[].psaProjectId` | number | no | The PSA project of the allocation. It's ignored on update, because an allocation can't change project. It's a numeric key, not the UUID that GET psa/projects/:id takes. |
| `allocations[].memberEmployeeId` | number \| null | no | The employee on the allocation. It's ignored on update. To reassign the allocation, send memberId. |
| `allocations[].memberPlaceholderId` | number \| null | no | The placeholder on the allocation. It's ignored on update. To reassign the allocation, send memberId. |

```json
{
  "allocations": [
    {
      "id": "3f2a91c7-5d84-4b1e-9c60-8a7e2d4f0b13",
      "totalHours": "32.00"
    },
    {
      "id": "b7c40e29-1af6-42d8-8e55-6d3b9c018a74",
      "memberId": 51204,
      "projectActivityId": 8317,
      "startDate": "2026-09-01",
      "endDate": "2026-11-30",
      "totalHours": "160.00",
      "method": "hoursPerWeek",
      "notes": "Rescoped after the change order.",
      "workingDays": [
        "Monday",
        "Tuesday",
        "Wednesday",
        "Thursday"
      ],
      "memberEmployeeId": 3889611,
      "psaProjectId": 32341
    }
  ]
}
```

## Response

`200` Success

```json
{
  "data": {},
  "diagnostics": [
    {
      "code": "<code>",
      "message": "<message>",
      "severity": "error",
      "path": [
        "<path>"
      ],
      "details": "<details>"
    }
  ]
}
```

## Response headers

- `Idempotency-Replayed` — Present and `true` only when this response replays a previously stored one for the same Idempotency-Key, rather than reflecting a live execution. Absent on a live response - never sent as `false`.

## Errors

| Code | Status |
| --- | --- |
| `NOT_FOUND` | 400 |
| `IDEMPOTENCY_KEY_CONFLICT` | 409 |
| `IDEMPOTENCY_PAYLOAD_MISMATCH` | 422 |

## Statuses

- `400` — Invalid request or business failure. Codes: NOT_FOUND
- `401` — The request carries no valid access token.
- `403` — Not authorized
- `404` — Not found
- `409` — The Idempotency-Key is still being processed by another request.
- `422` — The Idempotency-Key was already used with a different request payload.
- `429` — Too many requests from this client address. The response has no body and no `Retry-After` header.
- `500` — Internal server error