Modify an order

v3.2 v3.3

Learn how to use /orders/modify to update payment card details, stay dates and room-level details for existing accommodation reservations. This guide covers supported modifications, request examples, response formats and error handling.

Use the orders/modify endpoint to update specific details within an existing accommodation reservation.

You can use this endpoint to change the following elements:

✅ Credit card details.
✅ Checkin and checkout dates.
✅ Room-level details (guest allocation, guest names, and smoking preferences).

• You need the order ID and, for accommodation modifications, the accommodation reservation ID.
• For room-level changes, you also need the room reservation ID.
• Use /orders/details/accommodations to retrieve the reservation and room reservation identifiers and verify the current reservation details.

Before applying your changes, you can optionally validate and estimate changes before applying them.

If available to your integration, use /orders/modify/preview before /orders/modify.

Send a request to orders/modify endpoint with the following fields:

To update the payment card for an eligible reservation:

1. Use the modification.payment object.
2. Set type to "card".
3. Include the following fields in the change object:

• 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": "4334069995",
  "modification": {
    "payment": {
      "type": "card",
      "change": {
        "number": "4111111111111111",
        "cvc": "737",
        "cardholder": "Jon Snow",
        "expiry_date": "2030-03"
      }
    }
  }
}

{
  "modifications": {
    "payment": {
      "status": "successful"
    }
  }
}

To change the stay dates:

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

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

In the case of dates modification, the response includes the new price for the modified reservation.

{
  "data": {
    "modification": {
      "accommodation": {
        "new_price": 78.25,
        "status": "successful"
      }
    }
  },
  "request_id": "UmFuZG9tSVYkc2RlIyh9YV3CugMXEW9cxCXzj8lTlg8gbGIrozNJUJEQ1pFr+WkAk9uAy/KRmk5J3xi9Yw1h0Xy4jTiofhCe/XCmws8MfGEjI253Pagi+Q=="
}

You can update guest names, the number of adults allocated to a room and smoking preferences.

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

• room_reservation ID (string).
• guests.name - Update the guest name.
• 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": "John Doe" },
          { "name": "Jenny Doe" }
        ],
        "smoking_preference": "smoking"
      }
    }
  }
}

{
  "data": {
    "modification": {
      "accommodation": {
        "status": "successful"
      }
    }
  },
  "request_id": "UmFuZG9tSVYkc2RlIyh9YUdRpaDGn9Pw2aEu"
}

• Separate requests per modification type - Room, card, and date updates must be done in separate requests. Ensure you only modify one aspect at a time.
• Room-level updates - These apply to individual room reservations, not the entire booking.
• Wait time - Allow at least 5 minutes between modification requests to the same order to prevent conflicts.
• Check payment outcomes - When the detailed response is returned, check both modification and payment statuses. A successful modification does not necessarily mean payment succeeded.

The 3.3 accommodation modification response can use either of two formats. Always inspect the fields returned rather than assuming that an HTTP 200 response means the requested modification succeeded.

The detailed format is used for modifications requiring payment processing, such as a date change that increases the reservation price. The booking modification may succeed even if payment is still pending or has failed.

{
  "modification": {
    "accommodation": {
      "status": "failed"
    }
  }
}

A failed status means the modification did not succeed. Check the reservation's current details before deciding whether to submit another request.

{
  "modification": {
    "accommodation": {
      "modification_status": "successful",
      "payment_status": "successful",
      "message": "Modification and payment completed successfully.",
      "new_price": 181.44
    }
  }
}

Both the accommodation modification and payment have succeeded.

{
  "modification": {
    "accommodation": {
      "modification_status": "successful",
      "payment_status": "pending",
      "message": "Modification was successful but the payment is pending. Check the payment status using /orders/details.",
      "new_price": 181.44
    }
  }
}

The modification succeeded, but payment processing is not complete.

Check the latest payment status using /orders/details before treating payment as completed.

{
  "modification": {
    "accommodation": {
      "modification_status": "successful",
      "payment_status": "failed",
      "message": "Modification was successful but the payment failed. Check the payment status using orders/details.",
      "new_price": 181.44
    }
  }
}

The modification succeeded, but the payment failed.

• Use /orders/details to check the current payment status and follow the appropriate payment recovery process for your integration.
• Do not interpret modification_status: "successful" as confirmation that payment succeeded.

Modifying dates or room occupancy may affect the reservation price. To avoid unexpected costs:

1. Use the accommodations/availability endpoint to review current availability and prices before submitting the modification.
2. Review the modification response to determine whether the change succeeded and, if present, whether payment succeeded.
3. For a pending or failed payment, use /orders/details to check its current status, as described in the new 3.3 response guidance.
4. If the requested change cannot be made at an acceptable price, assess whether cancellation and a new booking are appropriate under the applicable policies.

Modification requests may fail because of invalid reservation details, unsupported changes or room restrictions.

If the modification fails, check the returned status or error message to identify the issue before submitting another request.