---
title: "Add Stay To Trip"
method: POST
path: "/v1/trips/{trip_id}/stays"
tags: ["mcp-server"]
---

# Add Stay To Trip

`POST /v1/trips/{trip_id}/stays`

Record a booked stay — it lands in Bookings, not as a place card.

A hotel added through add_place_to_guide becomes an attraction: no dates, no
confirmation number, and it never appears alongside the flights and other
reservations. This is the same `add_stay` the in-app Add-stay flow calls, so
the stay is geocoded, canonical-stamped, date-synced and enqueued for
enrichment identically — only the authentication differs.

## Path parameters

- `trip_id` string, uuid, required

## Request body

- AddStayRequest
  - `address` string, required
  - `place_id` string, nullable
  - `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
  - `confirmation_number` string, nullable

## Response `200`

Successful Response

- AddStayResponse
  - `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)