---
title: "WRITE: push one plan day's saved-point stops to the end of the trip, so the rebuilt plan spreads them over later days —"
method: POST
path: "/actions/shift_trip_day"
tags: ["itinerary"]
---

# WRITE: push one plan day's saved-point stops to the end of the trip, so the rebuilt plan spreads them over later days —

`POST /actions/shift_trip_day`

## Request

- Base URL: `https://findinghorizons.ca/api/v1`
- URL: `https://findinghorizons.ca/api/v1/actions/shift_trip_day`
- Auth: OAuth 2 (authorization code, authorization URL `https://findinghorizons.ca/api/mcp/authorize`, token URL `https://findinghorizons.ca/api/mcp/oauth/token`, scopes: `itinerary:write`)

WRITE: push one plan day's saved-point stops to the end of the trip, so the rebuilt plan spreads them over later days — the move for a rained-out morning or a disrupted travel day. Bookings and detours stay put.

## Headers

- `Idempotency-Key` string, required
- `X-FH-Task` string

## Request body

- object
  - `tripId` string, required
  - `date` string, required: The plan day's date, YYYY-MM-DD (from build_trip_plan)
  - `today` string: The traveller's own date, YYYY-MM-DD, where the action needs one
  - `expectedVersion` integer: For a change to a trip: the planVersion you last read

## Response `200`

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

## Other responses

- `202`: Waiting for the traveller's approval in Finding Horizons
- `400`: Bad body / missing Idempotency-Key
- `401`: No or invalid token
- `403`: Scope not granted
- `409`: Conflict: the plan changed since expectedVersion, or the same key is still running
- `422`: The action said no
- `429`: Rate limited

---

[API](https://skmtc.dev/findinghorizons/apis/finding-horizons-api.md) · [All operations](https://skmtc.dev/findinghorizons/apis/finding-horizons-api/llms.txt) · [OpenAPI document](https://skmtc.dev/findinghorizons/apis/finding-horizons-api/revisions/e347f6070173?raw)