Redirects the end-user's browser straight to Airbnb's OAuth consent
screen without showing any Host Tools UI. After the owner consents,
Host Tools auto-imports every net-new listing from that Airbnb account
into the listing group associated with ownerImportToken, then
redirects the owner to the partner's redirect URL with result query
parameters appended.
This is a browser redirect URL, not a JSON endpoint. Send the owner's
browser to this URL — do not call it with fetch or axios.
Typical integration flow:
- Call
POST /api/listingGroups/{listingGroupID}/generateOwnerImportToken
to obtain anownerImportTokenfor the target listing group. - Construct the auto-connect URL with the token, your allowlisted
redirect
URL, and the desiredscope. - Redirect your end-user's browser to that URL.
- After Airbnb consent, the owner is redirected to your
redirectURL.
Readowner-import-statusto determine success or failure.
On success, the partner redirect receives:
?owner-import-status=success&imported=<n>&accountID=<id>
On failure, the partner redirect receives:
?owner-import-status=error&owner-import-error=<code>
where <code> is one of invalid-link, invalid-scope, oauth-denied,
oauth-failed, import-failed.
Listings that were already imported on this Host Tools user are skipped —
they are not re-imported or moved between groups. Only truly-new listings
are added to the group.
If the redirect parameter is missing or its domain is not allowlisted,
the endpoint returns a 400 ErrorModel response — this is the only path
that doesn't end in a 302, because there's no safe partner URL to bounce
the error to.
Only Airbnb supports headless auto-connect. Vrbo, Booking.com, and Houfy
still use the standard owner-import flow.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
302Redirect — either to Airbnb's OAuth consent screen (on valid token +
allowlisted redirect), or back to the partner's redirect URL with an
error code if token/scope validation fails.