Preview order modifications Beta

Learn how to use the /orders/modify/preview endpoint to check and validate changes in accommodation orders. This guide outlines required parameters, and practical examples to validate accommodation dates, room details or payment modifications.

Use the /orders/modify/preview endpoint to check whether a requested modification can be applied to an order and review its impact before confirming the change.

Use the preview endpoint to:

✅ Validate whether a modification is allowed before attempting it.
✅ Avoid failed modification requests.
✅ Show users the expected cost impact (for accommodation date changes)

Use this endpoint as an optional step before modifying an order:

1. Call /orders/modify/preview.
2. Check the modifiable field in the response.
3. If true, proceed with /orders/modify.

The endpoint supports previewing the following changes:

When making a request to the orders/modify/preview endpoint, you must include:

The request body always includes:

To check whether modifications in the payment card is possible:

1. Use the modification.payment object.
2. Set type to "card".
3. Include a "change" object with:

• number: The new credit card number.
• cvc: The card’s CVC code (3–4 digits).
• cardholder: The cardholder's name.
• expiry_date: The card's expiry date in YYYY-MM format.

{
  "order": "6520081014",
  "modification": {
    "payment": {
      "type": "card",
      "change": {
        "cardholder": "John Doe",
        "number": "4111111111111111",
        "expiry_date": "2027-12",
        "cvc": "123"
      }
    }
  }
}

To check whether an accommodation date modification is possible:

1. Use the modification.accommodation object to modify the dates.
2. Include the reservation ID.
3. Set type to "dates".
4. Include the new dates in change (checkin and checkout) using YYYY-MM-DD format.

{
  "order": "4297204980",
  "modification": {
    "accommodation": {
      "reservation": "4297204980",
      "type": "dates",
      "change": {
        "checkin": "2026-10-20",
        "checkout": "2026-10-21"
      }
    }
  }
}

To check whether it is possible to update room-level details such as guest names, allocation, or smoking preferences:

1. Use the modification.accommodation.
2. Set type to room.
3. Include the reservation ID.
4. In the change object, specify:

• room_reservation ID (string).
• guests[].name - Update the guest name(s).
• allocation.number_of_adults - Update number of adults.
• smoking_preference - Modify the smoking preference for the room ("smoking", "non_smoking", or "no_preference").

{
  "order": "5000375899",
  "modification": {
    "accommodation": {
      "reservation": "5000375899",
      "type": "room",
      "change": {
        "room_reservation": "5448643068",
        "allocation": {
          "number_of_adults": 2
        },
        "guests": [
          { "name": "Test Test" },
          { "name": "Test2 Test" }
        ],
        "smoking_preference": "smoking"
      }
    }
  }
}

All responses include:

• request_id – Unique identifier for the request.
• data.modifiable – Indicates whether the modification can be applied.

{
  "data": {
    "modifiable": false,
    "reason": "Modification not allowed for this reservation since this order has been cancelled."
  }
}

{
  "data": {
    "modifiable": true
  }
}

For date changes, the response includes updated pricing:

{
  "data": {
    "modifiable": true,
    "price": {
      "currency": "EUR",
      "current": {
        "amount": 200.00
      },
      "new": {
        "amount": 250.00
      }
    }
  }
}

Use this to:

• Show users the updated total cost.
• Highlight any price difference before confirmation.

• Price information is only returned for accommodation date changes.
• Not all modification scenarios may be supported.
• Behaviour and response fields may change as this endpoint is in Beta.