Publishes a listing that isn't on the channel yet: as a new Airbnb
listing (channel: Airbnb), or as a new room on one of the user's
Booking.com properties (channel: Booking).

Airbnb. The listing is created on one of the user's Airbnb
accounts. Host Tools creates it there with
the listing's name, address, base price as its nightly price, the room
type given, and all of its content and photos (see "Content sync" on
/api/setListing/{listingID}), then lists it with every date closed.
Its dates open once the listing's calendar sync is on
(syncAvailability, and syncPricing for the prices), from Host
Tools' calendar, as on any other listing.

The listing needs a name, a street address, a city, a country, a map
location, a currency and a base price. An Airbnb account connected in
setup mode can't publish, as it can't list a listing.

Booking.com. Each Booking.com account in /api/getAccounts is
one property. Booking.com adds a room only at its property's address:
a listing elsewhere needs a property of its own, which Host Tools
can't create yet. So a listing whose map location is more than 100 m
from the property's, and whose street address isn't the property's,
is refused with a 400 saying how far away it is. A room of the type
given is added to the property with the
listing's rooms and beds and maximum guests, then gets the rest of the
listing's room content: its room amenities, bathrooms, smoking
policy, fees and photos. The property's own address, name,
description, photos, check-in and check-out times, pets and children
policies and amenities, which every room of it shares, stay as they
are on Booking.com. A later edit of one of them goes out with content
sync, as for any listing on the property. Booking.com then checks
the property, and if a check names the new room (for example, it has
no amenities, or an apartment property's room has no kitchen), the
room is deleted and that's the failure. A check that the room has no
photos waits for them: Booking.com checks the room again once they're
on it. A check the property fails on
its own (a contract, invoice details) doesn't stop the publish. The
room has no rate and can't be booked until the listing's calendar
sync is on, which gives it Host Tools' prices and availability. The
listing needs beds and a maximum number of guests.

Either channel. The listing's content sync is turned on. When it
was off, the listing's content also goes to the other channels it's
on, replacing their text and photos, as turning content sync on with
/api/setListing/{listingID} does.

The publish is queued, so this answers 202. It takes a minute or
two, and on Booking.com up to half an hour while it processes the
photos. /api/getListing/{listingID} shows it in publishing until
the listing is on the channel (channels). If the channel refuses
it, Host Tools deletes what it created there, and the failure is a
listing.publishFailed error (a type: "error" webhook and
/api/getErrors) with the channel's reason.