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

# Add Event To Trip

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

## Request

- Base URL: `https://stardrift.ai` (the document declares no server; this is the origin it was published from)
- URL: `https://stardrift.ai/v1/trips/{trip_id}/events`
- Auth: none declared

Record something scheduled that isn't a booking — a wedding, a concert.

add_place_to_guide would make it an attraction, which is what a place the
user might visit is, not something happening at a time they are expected at.
An event carries its own start and end, and its venue is geocoded to a pin
when one resolves. This is the same `add_event` the in-app Add-event flow
calls; only the authentication differs.

## Path parameters

- `trip_id` string, uuid, required

## Request body

- AddEventRequest
  - `name` string, required
  - `start_datetime` string, date-time, nullable
  - `end_datetime` string, date-time, nullable
  - `venue_name` string, nullable
  - `address` string, nullable
  - `place_id` string, nullable
  - `category` string, nullable
  - `description` string, nullable
  - `city` string, nullable
  - `total_price` number, nullable
  - `currency` string
  - `confirmation_number` string, nullable

## Response `200`

Successful Response

- AddEventResponse
  - `activity_id` string, required
  - `activity` object, required
  - `warnings` string[]

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/stardrift/apis/stardrift-api.md) - [All operations](https://skmtc.dev/stardrift/apis/stardrift-api/llms.txt) - [OpenAPI document](https://skmtc.dev/stardrift/apis/stardrift-api/revisions/be9ed1e6c38a?raw)