OpenTrip Docs
BackendHTTP API

API (client contract)

API (client contract)

HTTP contract for web, mobile, and other clients.

Source of truth for routes: apps/api/src/interfaces/http/app.ts. Request shapes: edge Zod schemas (including application/trip/ops/schemas.ts). Response DTOs: application serializers (application/dto.ts, agent/preferences DTOs, invite service types, weather/FX data types).

Mobile / multi-client start here.

Contents

DocWhat it covers
conventions.mdBase path, envelopes, status codes, trip access, non-JSON, amounts/dates/ids
auth-session.mdSession cookies, Better Auth surfaces for all clients
routes.mdFull method/path/auth route index
platform.mdHealth, uploads, weather, FX, agent status
trips.mdList / create / get / rename trips
itinerary.mdDays, stops, votes, comments, media
expenses.mdAdd / update expenses
reservations.mdBooking lifecycle and optimistic concurrency
invites.mdCreate, preview, accept invites
user.mdPreferences and avatar
agent-endpoints.mdAgent messages, chat stream, events, suggestions
dtos.mdResponse/request DTO field catalog
errors.mdError envelope and code mapping
multi-client.mdPractical notes for native / multi-client apps

On this page