itinerary

Build the full day-by-day plan for one of the user's trips FROM THEIR OWN saved points: days honoring the trip's pace, t

Build the full day-by-day plan for one of the user's trips FROM THEIR OWN saved points: days honoring the trip's pace, transport blocks between city hops (booked flights/trains with airport-survival lead-ins, or mode recommendations weighted by budget), and every ≥4-hour gap with filler suggestions from live events and community points. This runs the app's own deterministic planner — no server-side AI; you (the connected assistant) do the reasoning on top. It is a READ: it shows the plan as it stands and changes nothing (it never adds saves to the trip or saves the plan).

post/actions/build_trip_plan

Request

  • Base URL: https://findinghorizons.ca/api/v1
  • URL: https://findinghorizons.ca/api/v1/actions/build_trip_plan
  • Auth: OAuth 2 (authorization code, authorization URL https://findinghorizons.ca/api/mcp/authorize, token URL https://findinghorizons.ca/api/mcp/oauth/token, scopes: itinerary:read)

Request body

tripIdstring required

Trip id from get_my_trips

todaystring

The traveller's own date, YYYY-MM-DD, where the action needs one

Response

Done — { ok, api, action, result, card, operation? }

Changes

No recorded changes to this operation across all 1 revision of this API.