Manage Airbnb Listings

API sync is authorised per listing

Airbnb turns API sync on one listing at a time, not once for the account. Each listing carries its own sync category, and a listing whose category is none is closed to the API — Airbnb refuses every write to it even though the account is connected and every other listing on it writes fine. Reconnecting the Airbnb account does not change a listing's sync category. Only someone with access to the listing on Airbnb can turn sync on for it, on the listing itself.

• sync_all — Repull manages content, rates and availability. Every write on this page works.
• sync_rates_and_availability — Repull manages rates and availability; listing content is managed by the host on Airbnb.
• none — the listing is not connected to Repull on Airbnb at all. Every write returns 403 listing_not_api_connected and nothing is sent to Airbnb, so nothing is partially applied.
• To tell which is which, read GET /v1/channels/airbnb/listings: every entry of each listing's connections[] carries syncCategory (one of the three above, or null if it has never been reported) and writable — false exactly when syncCategory is none. Check writable before a write and you never send one that cannot land. Full detail: https://repull.dev/docs/errors/listing_not_api_connected

Cover photos for a selection screen

A screen where someone picks properties — which ones to manage, which to push a rate change to, which to put in a report — needs a picture next to each name. ?include=thumbnail puts one on every row of this list, so the screen renders from a single request.

• thumbnailUrl is the property's cover photo, a plain image URL you can put straight in an <img src>. It does not expire and needs no authentication.
• It sits on the listing, not on each connection: every Airbnb connection under a property shows the same property, so the picture is the same for all of them.
• null means the property has no cover photo yet. The property is still returned — never filter a row out because its picture is missing, or someone loses a property they were looking for.
• The field is absent, not null, when you do not ask for it. That is how you can tell "no photo" apart from "I did not request photos".
• It costs nothing: the photo comes back on the query this endpoint already runs, so asking for it does not make the call slower and does not use extra credits.
• For properties that are not connected to Airbnb, or ones you have deactivated, use GET /v1/listings?status=all&include=thumbnail instead — same field, your whole catalog.

curl 'https://api.repull.dev/v1/channels/airbnb/listings?include=thumbnail' \
  -H "Authorization: Bearer sk_live_YOUR_KEY"

# {
#   "data": [
#     {
#       "listingId": 6248,
#       "name": "Oceanview Villa",
#       "city": "Malibu",
#       "thumbnailUrl": "https://a0.muscache.com/im/pictures/oceanview.jpg",
#       "connections": [ ... ]
#     },
#     {
#       "listingId": 6249,
#       "name": "Harbor Loft",
#       "city": "Malibu",
#       "thumbnailUrl": null,
#       "connections": [ ... ]
#     }
#   ]
# }

Several Airbnb accounts

A workspace can connect more than one Airbnb account. By default this route returns every connected account's rows; pass ?account_id=<airbnb host id> to scope to one. Every row carries accountId + accountName either way (the older hostId / hostName remain as aliases), so you can group without a second call. Airbnb host ids exceed 2^53 — keep them as strings and never parse them as numbers: Number("1000000000000000002") is 1772489413932732200, a different account, and returns 404. A two-account walkthrough lives on the Account scope page (/docs/scoping).

# Every connected account — the default, unchanged
curl 'https://api.repull.dev/v1/channels/airbnb/listings' \
  -H "Authorization: Bearer sk_live_YOUR_KEY"

# Just one account
curl 'https://api.repull.dev/v1/channels/airbnb/listings?account_id=1000000000000000002' \
  -H "Authorization: Bearer sk_live_YOUR_KEY"

# An id this workspace has not connected — 404, with your own ids to copy
# {
#   "error": {
#     "code": "not_found",
#     "message": "No connected Airbnb account `1772489413932732200` in this workspace.",
#     "field": "account_id",
#     "value_received": "1772489413932732200",
#     "valid_values": ["1000000000000000002", "80000001"]
#   }
# }

Data freshness

Airbnb reads are served from Repull's local mirror and never call Airbnb upstream, so every response carries a dataFreshness envelope telling you whether to trust it. lastSyncedAt is the last import that actually landed data — a run that failed or was rate-limited never moves it. accounts[] gives the verdict per connected account; it is omitted when the workspace has no Airbnb account to attribute.

• Top-level stale: true means every connected account is stale — nothing in the response is current. For the single-account workspace this is exactly the old behaviour.
• Top-level stale: false with reason: "partial_account_staleness" means some accounts are fine and some are not. The response is usable; read accounts[] to see which rows to distrust. The reason is emitted deliberately even though stale is false, so a consumer reading only the aggregate is never told everything is fine while one account is down.
• Top-level stale: false with no reason means every account is current.
• With ?account_id=, accounts[] holds exactly that account and the top-level fields mirror it.
• reason is one of host_disconnected_since_<iso>, host_disconnected, host_not_activated, sync_lag_>_24h, never_synced, or partial_account_staleness. fixUrl is the dashboard screen that resolves it.

{
  "dataFreshness": {
    "lastSyncedAt": "2026-09-18T04:12:09.000Z",
    "stale": false,
    "reason": "partial_account_staleness",
    "fixUrl": "https://repull.dev/dashboard/connections",
    "accounts": [
      {
        "accountId": "1000000000000000002",
        "accountName": "Seaside Stays",
        "lastSyncedAt": "2026-09-18T04:12:09.000Z",
        "stale": false
      },
      {
        "accountId": "80000001",
        "accountName": "Casey",
        "lastSyncedAt": null,
        "stale": true,
        "reason": "host_disconnected",
        "fixUrl": "https://repull.dev/dashboard/connections"
      }
    ]
  }
}

Unlist, relist, push and delete

Every action on one Airbnb listing is a POST /v1/channels/airbnb/listings/{id} with an action in the body. {id} is the Repull listing id. airbnbConnectionId is the id of one entry in that listing's connections (see the list above): a listing can be on more than one Airbnb account, so the actions that change Airbnb ask which one.

• unlist — { "action": "unlist", "airbnbConnectionId": 456 }. Takes the listing off Airbnb so it cannot be booked. The listing, its content, photos and reviews stay on Airbnb, and existing reservations are not affected.
• relist — { "action": "relist", "airbnbConnectionId": 456 }. Puts an unlisted listing back up. It sends nothing else: the content on Airbnb is what it was when you unlisted.
• Relisting a listing Airbnb has already approved does not send it back for review: it is bookable again straight away. Tested on a live listing: has_availability was back to true at once and still true 20 seconds later.
• Both read the listing back from Airbnb before answering. verified: true means Airbnb now shows the state you asked for. If Airbnb accepts the call but the listing is still live (unlist) or still offline (relist), you get an error, never a success. verified: false means the read-back could not run: treat it as unknown and read the listing again.
• push or publish — { "action": "push", "airbnbConnectionId": 456 }. Sends the listing's current content to the Airbnb listing. To create a new Airbnb listing, send hostId instead of airbnbConnectionId, or use POST /v1/listings/{id}/publish/airbnb (the same thing, and it returns what each part of the listing did).
• delete — { "action": "delete" }. Deactivates the listing in Repull only. It does not delete, or even unlist, anything on Airbnb. Nothing in this API deletes an Airbnb listing; to stop bookings, unlist first. Sending delete twice is safe.
• To take a listing off every channel at once (Airbnb and Booking.com), use POST /v1/listings/{id}/offline and POST /v1/listings/{id}/online instead: one call, one result per channel.

curl -X POST https://api.repull.dev/v1/channels/airbnb/listings/123 \
  -H "Authorization: Bearer sk_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"action": "relist", "airbnbConnectionId": 456}'

# {
#   "data": {
#     "id": 123,
#     "action": "relist",
#     "channel": "airbnb",
#     "airbnbConnectionId": 456,
#     "live": true,
#     "verified": true
#   }
# }