# Sync the itinerary with the design

> The sync_itinerary MCP tool: sync the itinerary with the design.

`sync_itinerary` · writes · idempotent

[REST: `POST /v1/trips/{tripId}/itinerary/sync`](https://api.bymundi.com/docs/reference/itinerary.sync.md)

## What the model reads

Does what opening the Itinerario tab does in the app: rebuilds the days from the trip's design and latest quote (creating them the first time), then rewrites stop times planned by an older planner. Call it after changing a trip's `design`. `skipped` is true when the trip has no route. It records no change and has no undo; it is idempotent, and a second run changes nothing.

Permissions: trips:write.
This cannot be undone.

## Input

| Field | Type | Required | Description |
|---|---|---|---|
| `tripId` | uuid | yes |  |

## Input schema (JSON)

```json
{
  "type": "object",
  "properties": {
    "tripId": {
      "type": "string",
      "format": "uuid"
    }
  },
  "required": [
    "tripId"
  ],
  "additionalProperties": false
}
```