v2/accept-reservation-alteration

Params

Description

Accept a guest's Airbnb alteration request by alteration_id, as received in the reservation_alteration webhook.

Returns request_uid; see the get-request-status method for the result.

This endpoint requires the following scope: airbnb-reservations

Airbnb requests to book and alteration requests

Requires the airbnb-reservations scope, which is granted on request. Direct bookings are unaffected: v2/accept-reservation and v2/decline-reservation still need direct-bookings for them.

• v2/accept-reservation and v2/decline-reservation act on an Airbnb request to book when reservation_code is an Airbnb reservation in pending status.
• v2/accept-reservation-alteration and v2/decline-reservation-alteration act on a guest's alteration request in pending status. Send alteration_id as received in the reservation_alteration webhook.
• To decline a request to book, send decline_reason and a non-empty message to the guest. decline_reason is one of:
  • dates_not_available: requested dates are not available, the dates are blocked on the calendar
  • not_a_good_fit: the listing is not a good fit for the guest's needs (children, pets, etc.)
  • waiting_for_better_reservation: waiting for a more attractive reservation
  • not_comfortable: not comfortable with this guest
• An alteration decline takes no reason and no message.

Result of an Airbnb action

The call is queued: the response holds status and request_uid, and the sample below shows the Airbnb case. Airbnb answers later. Pass request_uid to get-request-status: completed means Airbnb accepted the action, error means the action failed and request_error holds the reason. Usually Airbnb rejected it, but an error also follows an action Airbnb applied when iGMS failed to sync the result, so check the booking before retrying.

{
    "status": 0,
    "request_uid": "74302303"
}