---
title: "Move Booking To Trip"
method: POST
path: "/bookings/{booking_id}/move"
tags: ["bookings"]
---

# Move Booking To Trip

`POST /bookings/{booking_id}/move`

Re-file a misfiled email-imported booking onto another trip.

The move pins the booking where the user put it: the new membership link is
written with ``run_id=None``, which every later reconcile reads as
human-placed and refuses to move.

## Path parameters

- `booking_id` string, uuid, required

## Request body

- MoveBookingRequest — Where the user wants this booking to live instead. Exactly one of ``trip_id`` / ``create_trip``. ``confirm`` acknowledges the plan entries the move would strip, mirroring the itinerary remove endpoint.
  - `trip_id` string, uuid, nullable
  - `create_trip` boolean
  - `confirm` boolean

## Response `200`

Successful Response

- MoveBookingResponse
  - `needs_confirmation` boolean
  - `affected_plan_days` integer[], nullable
  - `trip_id` string, nullable
  - `trip_title` string, nullable
  - `created_trip` boolean
  - `archived_trip_id` string, nullable
  - `source_trip_id` string, nullable
  - `conversation_id` string, nullable

## Other responses

- `422` — Validation Error

---

[API](https://skmtc.dev/stardrift/apis/fastapi.md) · [All operations](https://skmtc.dev/stardrift/apis/fastapi/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/stardrift/fastapi/revisions/00746572572a/schema)