Below is a list of Booking.com statuses that Guesty cannot handle via API. Rather than creating a Jira in these cases, we would require the assistance of Booking.com.
According to Booking.com, their local Support team should be contacted (rather than the Connectivity team) as they are unable to modify property statuses.
According to Booking.com, their local Support team should be contacted (rather than the Connectivity team) as they are unable to modify property statuses.
Status | Not to be confused with |
|---|---|
Auto closed (content) | Not to be confused with XML: Auto closed content. |
Auto closed (geo) | - |
Being built | Not to be confused with XML: Being built. |
Being built (content) | Not to be confused with XML: Being built. |
Being built (on hold) | Not to be confused with XML: Being built. |
Change of Ownership Closed | - |
Closed - operations | - |
Closed - partner behavior | - |
Closed - ready to reopen | - |
Closed - waiting DD mandate | - |
Closed (bankruptcy) | - |
Closed (invoice not paid) | - |
Closed (rejected direct debit) | - |
Closed for fraud | - |
Closed for Fraud - Blocking Billing | - |
Closed forever | - |
Closed Forever Book-Off | - |
Closed forever: technical reasons | - |
Closed Post Legal | - |
Collecting Agency Closed | - |
Contacted | - |
Duplicate | Not to be confused with XML: Hotel is Duplicate. |
End of contract | - |
Interested | - |
Not Eligible | - |
Not interested | - |
NULL | - |
Parked business | - |
Pending approval - Booking.com BV | - |
Ready to open | - |
SB: Not synced | - |
Switching currency - Not in use | - |
Temp. closed for technical reasons | - |
Comments
0 comments
Please sign in to leave a comment.