# Create Team Members

`POST /psa/team-members/bulk`

Group: PSA › Team Members · Operation ID: `createTeamMembers`

Adds people or placeholders to a PSA project's team, optionally assigning each to a position. Either all are added, or none are.

Each entry names exactly one of employeeId or placeholderId, and optionally a projectPositionId. An entry with a position creates a position assignment and returns its id. An entry without one adds the person to the team but creates no assignment, so it returns no id. The response holds only the created ids, so it can be shorter than the input and is not aligned to it position by position. Adding people needs edit permission on the project.

[Open in the interactive reference](https://docs.api.lensing.ai/?op=createTeamMembers)

## Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `Api-Version` | header | `"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`: createTeamMembersInput.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `psaProjectId` | number | yes | The PSA project to add the people to. It is a numeric package-layer key, not the UUID that GET psa/projects/:id takes. Adding people needs edit permission on this project. |
| `assignments` | array of object | yes | One entry per person or placeholder to add. Each entry needs exactly one of employeeId or placeholderId. Either all are added, or none are. |
| `assignments[].employeeId` | number | no | The employee to add. Give either employeeId or placeholderId, not both. The employee joins the team even when projectPositionId is omitted. It is a numeric package-layer key. |
| `assignments[].placeholderId` | number | no | The placeholder to assign. Give either employeeId or placeholderId, not both. A placeholder entry with no projectPositionId creates nothing. It is a numeric package-layer key. |
| `assignments[].projectPositionId` | number or null | no | The project position to assign this person or placeholder to. Omit it to add the person to the team without a position assignment. It is a numeric package-layer key. |

Example:

```json
{
  "psaProjectId": 32341,
  "assignments": [
    {
      "employeeId": 3845142,
      "projectPositionId": 7
    },
    {
      "placeholderId": 91
    }
  ]
}
```

## Response

`200` Success

Under `data` (createTeamMembersOutput):

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `created` | array of object | yes | The ids of the position assignments created, in the order the entries were sent. An entry that created no position assignment contributes no id, so this can be shorter than the input. Read a record back with GET psa/team-member-positions/:id. |
| `created[].id` | string | yes | The unique identifier of the created position assignment. This is the id GET psa/team-member-positions returns. |

## 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 |
| --- | --- |
| `INVALID_ASSIGNMENT` | 400 |
| `IDEMPOTENCY_KEY_CONFLICT` | 409 |
| `IDEMPOTENCY_PAYLOAD_MISMATCH` | 422 |

## Statuses

- `400` — Invalid request or business failure. Codes: INVALID_ASSIGNMENT
- `401` — Missing or invalid 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
- `500` — Internal server error