---
title: "Moves a Membership"
method: POST
path: "/api/2026-10-01/resources/teams/memberships/move"
tags: ["Teams > Membership"]
---

# Moves a Membership

`POST /api/2026-10-01/resources/teams/memberships/move`

## Request

- Base URL: `https://api.factorialhr.com`
- URL: `https://api.factorialhr.com/api/2026-10-01/resources/teams/memberships/move`
- Auth: one of:
  - OAuth 2
    - Authorization code: `https://id.factorialhr.com/oauth/authorize`
    - Token URL: `https://id.factorialhr.com/api/oauth/token` scopes: `employees`
  - API key in header `x-api-key`

Move a membership to a different team in one operation (the employee is removed from the current team and added to the destination). Requires the nested teams feature and permission to manage both teams. Only direct memberships can be moved — moving an inherited row is rejected.

## Request body

- object
  - `id` string, required: ID of the membership to move (must be a direct membership)
  - `destination_team_id` string, required: ID of the destination team
  - `lead` boolean: Whether the employee should be a lead in the destination team. Omit it to keep the membership's current lead flag; pass false to move the employee and drop their leadership. Worth being explicit when restructuring: omitting it carries leadership across, so a lead of a small team who lands in a large one leads the large one.

## Response `200`

OK

- TeamsMembership
  - `id` string, required: Membership ID
  - `company_id` string: Company ID of the membership
  - `employee_id` string, required: Employee ID of the membership
  - `team_id` string, required: Team ID of the membership
  - `lead` boolean, required: Whether the employee is a lead of the team or not
  - `source_team_ids` string[], required: IDs of the teams this membership originates from (nested teams). In a company with nested teams, a direct membership includes the team itself; an inherited one, the sub-team(s) where the employee is a direct member. Only populated on reads that compute source attribution — reads filtered by a single team, or by a single employee with `with_source_attribution` enabled. Empty otherwise, including create, update and delete responses, and always empty for companies without nested teams. An empty array does not distinguish "computed and genuinely empty" from "not computed for this read" or "could not be computed", so only apply attribution-dependent logic to a read you explicitly shaped for it. A team-anchored read stops attributing above roughly a thousand members of the filtered team: past that the attribution is not computed at all and every row comes back empty, behind a normal `200`.
  - `parent_team_ids` string[], required: IDs of the ancestor teams that receive an inherited membership through this row (nested teams) — the teams this membership rolls up into. Populated under the same conditions as `source_team_ids`; empty otherwise.
  - `direct` boolean: Whether the employee is a direct member of the team (nested teams). Always present. `true` means direct member; `false` means the row exists only through inheritance from a sub-team; `null` means not computed for this read. Only computed on reads filtered by a single employee with `with_source_attribution` enabled — always `null` otherwise, including create, update and delete responses and companies without nested teams. `null` is also returned when directness could not be resolved for a transient reason, even with `with_source_attribution` enabled, so never treat `null` as `false` — retry the read instead.

## Changes

- **2026-11-03** `83ac9aa1de50`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/factorialhr/apis/factorial-api/changes/api/2026-10-01/resources/teams/memberships/move/post.md)

---

[API](https://skmtc.dev/factorialhr/apis/factorial-api.md) - [All operations](https://skmtc.dev/factorialhr/apis/factorial-api/llms.txt) - [OpenAPI document](https://skmtc.dev/factorialhr/apis/factorial-api/revisions/83ac9aa1de50?raw)