Reorder an existing node by moving it to a new position.
updateSequenceNode instead.
/api/campaigns/{id}/sequence/nodes with other verbs. See the sibling page for related operations on the same resource.Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Campaign UUID
^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$Draft-only. Both fields are required.
UUID of the node to move. Must belong to this campaign.
^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$Target 0-indexed position. Other nodes shift to accommodate the move.
0 <= x <= 9007199254740991Node moved. Returns the fresh ordered list of sequence nodes. Falls back to { mutated: true } if the post-mutation read-back fails.
Successful mutation response. The server re-fetches the full sequence and returns it so clients don't have to round-trip a GET.
Fresh ordered list of nodes after the mutation. Absent (replaced by mutated: true + optional node_id) only if the server's best-effort read-back after the mutation failed.