---
title: "Update Stay On Itinerary"
method: PATCH
path: "/trips/{trip_id}/stays/{stay_id}"
tags: ["stays"]
---

# Update Stay On Itinerary

`PATCH /trips/{trip_id}/stays/{stay_id}`

Correct a stay in place — its name, dates, price or confirmation.

Not its address: re-pinning would have to re-geocode and re-resolve the
property, and a stay pinned to the wrong place is still delete-and-re-add.

## Path parameters

- `trip_id` string, required
- `stay_id` string, required

## Headers

- `x-client-id` string, nullable

## Request body

- UpdateStayRequest — Fields to change on an existing stay. Omit one to leave it alone. None means "leave alone" rather than "clear", matching UpdateStayAction — so this cannot blank a field. Clearing would need a separate signal and no caller has wanted one.
  - `name` string, nullable
  - `check_in_date` string, date, nullable
  - `check_out_date` string, date, nullable
  - `check_in_time` string, time, nullable
  - `check_out_time` string, time, nullable
  - `total_price` number, nullable
  - `currency` string, nullable
  - `confirmation_number` string, nullable
  - `is_booked` boolean, nullable

## Response `200`

Successful Response

- UpdateStayResponse — Same shape as AddStayResponse — the edited stay, re-rendered.
  - `stay_id` string, required
  - `hotel` object, required

## 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)