Request a member genealogy move
Requires the bearer member’s current rep eligibility and movement policy. The moved node and destination must remain within the member’s current team; no member or actor selector is accepted. HTTP move admission is disabled unless the company is explicitly included in GENEALOGY_MOVE_COMPANY_IDS after migration prerequisites are satisfied. Return 200 only when applied or unchanged, and 202 with a human approval request or durable full-validation job. Clients cannot request unbounded synchronous execution. No legacy sponsor-axis value is changed by this endpoint. The example uses illustrative fixture IDs. Substitute records visible to your authenticated company or member.
Authorizations
A member credential for the member's own team — a member or customer session JWT, or a member's user token. Company service tokens are refused.
Headers
Optional client key that makes the request safe to retry. The first request with a key is evaluated and its outcome recorded; a retry with the same key and the same proposal replays that outcome, with the resource's current state, instead of moving again. The same key with a different proposal is refused with 409 idempotency_key_reused. Keys are scoped to the authenticated actor and tree; failed requests record nothing. While moves are paused for the company the request returns 503 without reading or recording the key, so retry it later with the same key. A recorded outcome is kept for at least 24 hours and then removed by an hourly cleanup; until it is removed the same key still replays it, and only after removal is the key evaluated as a new request. Retry within 24 hours to be sure of a replay.
1 - 255^[!-~]+$Path Parameters
Moving node identifier in the authenticated company and permitted team.
Body
An explicit unilevel move proposal. Actor and source are derived from authentication.