비즈니스 로직 오류로 인해 예약을 업데이트하지 못하면 오류가 UpdateBookingResponse.booking_failure 필드에 채워지고 HTTP 상태 200으로 반환됩니다.
요청
UpdateBookingRequest
요청 메시지에는 예약 필드에 업데이트된 정보가 포함됩니다.
요청에 업데이트할 예약을 식별하기 위한 booking_id가 포함됩니다. 또한 다음 중 하나가 포함됩니다.
업데이트할 슬롯 세부정보(예약 수정)
변경할 상태(예약 취소)
변경이 필요하지 않은 필드는 요청에 제공되지 않습니다.
반환값
UpdateBookingResponse
// Request to update a Booking.messageUpdateBookingRequest{// The booking to be updated// The following fields can be set in a booking:// - status, to cancel a booking.// - one of the following is required:// - start_time AND duration in the slot, to reschedule a booking.// - party_size (for dining reservations).Bookingbooking=1;}// Response with the updated Booking.messageUpdateBookingResponse{// The updated booking (required)Bookingbooking=1;// The updated user payment option originally used to pay for this booking.// This should be set if the UpdateBookingRequest results in a change to// the UserPaymentOption.// For instance, if the booking is canceled, the UserPaymentOption should// reflect an additional credit to the user. In the case of a multi-use// payment option, the current_count should be increased by one to// allow the user to create another booking with this payment option. In the// case of a single-use payment option, a new single-use user payment option// should be returned. (required if altered in update)UserPaymentOptionuser_payment_option=2;// If updating a booking fails, this field should reflect the business logic// error (e.g., booking is not cancellable) (required if failure occurs)BookingFailurebooking_failure=3;}
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["필요한 정보가 없음","missingTheInformationINeed","thumb-down"],["너무 복잡함/단계 수가 너무 많음","tooComplicatedTooManySteps","thumb-down"],["오래됨","outOfDate","thumb-down"],["번역 문제","translationIssue","thumb-down"],["샘플/코드 문제","samplesCodeIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-07-26(UTC)"],[[["\u003cp\u003eUpdateBooking API allows clients to modify or cancel existing bookings by providing the \u003ccode\u003ebooking_id\u003c/code\u003e and updated information like slot details or status.\u003c/p\u003e\n"],["\u003cp\u003eThe API uses \u003ccode\u003eUpdateBookingRequest\u003c/code\u003e for sending update requests and \u003ccode\u003eUpdateBookingResponse\u003c/code\u003e for responses, including the updated booking and potentially an updated user payment option.\u003c/p\u003e\n"],["\u003cp\u003eIn case of update failure due to business logic errors, the error details will be provided in the \u003ccode\u003ebooking_failure\u003c/code\u003e field of the \u003ccode\u003eUpdateBookingResponse\u003c/code\u003e, even with an HTTP 200 status.\u003c/p\u003e\n"],["\u003cp\u003eWhen updating a booking results in payment option changes (e.g., cancellation leading to credit), the updated \u003ccode\u003eUserPaymentOption\u003c/code\u003e is included in the response.\u003c/p\u003e\n"]]],["The `UpdateBooking` process modifies or cancels a booking via an `UpdateBookingRequest`, identified by `booking_id`. The request includes either new slot details for modification or a status change for cancellation. The `UpdateBookingResponse` returns the updated `Booking` and may include an altered `UserPaymentOption` if changes occurred. If updating fails due to a business logic error, the `booking_failure` field is populated, and a 200 HTTP status is returned. Unchanged fields are omitted from the request.\n"],null,[]]