Update Activities

Two accepted shapes, deliberately:

itinerary_data: the legacy wholesale replace. The caller owns the entire itinerary and everything absent from the payload is gone.

days: the delta the live app actually sends: the complete activity list of each TOUCHED day, where each row carries only the keys the app knows (id + sort_order/is_completed/rating). Sending that through the wholesale path is what silently thinned stored activities down to four keys: descriptions, coordinates, prices and travel legs all lost on the first reorder. This branch MERGES instead: it is the only write path the app uses, and it can never remove a field or a row.

put/api/v1/itineraries/{externalId}/activities

Request

Base URL: https://www.endlesstravelplans.com
URL: https://www.endlesstravelplans.com/api/v1/itineraries/{externalId}/activities
Auth: HTTP bearer

Request body

itinerary_dataobject[]

The complete itinerary data (legacy wholesale replace). Required without days.

markersobject[]

Map marker data.

Example request

{
  "itinerary_data": [
    []
  ],
  "days": [
    []
  ],
  "markers": [
    []
  ]
}

Response

Example response

{
  "itinerary": {
    "external_id": "uuid"
  }
}

Changes

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