Fetching the full listing: content, details, rooms, policies, pricing, fees and taxes
Pull rich listing copy — descriptions, house rules, check-in times, bed counts, Wi-Fi credentials — in the same call you already use for your catalog. No second round-trip, no per-platform scraping.
Why this exists
Most apps that render a property-detail page need more than the name and a thumbnail. They need the public description, the space and neighbourhood blurbs, house rules, and the structural details a guest expects on a listing page — bedrooms, bed count, capacity, check-in times, Wi-Fi network, house manual.
Without these expansions, the only way to assemble that view was to call back into Airbnb (or whichever channel held the canonical text) on every page render. That's a rate-limited round-trip per listing per request, and it ties your front-end to whichever upstream is up.
With ?include=content and ?include=details, Repull serves both blocks straight from the synced data already in your workspace. One call, one bearer token, no upstream coupling.
Already using ?include=amenities?
?include=amenities,content,details returns everything in a single response — see Combining includes.The two new include keys
Both keys work on GET /v1/listings/{id} and GET /v1/listings. They're additive: each one drops a new object onto the listing payload. Neither is loaded by default — the base listing response stays small.
include=content
Adds a content object with the long-form listing copy. English locale by default.
content.summarystringnullableShort marketing summary shown at the top of the listing.
content.descriptionstringnullableThe main listing description — the long block of copy guests read first.
content.spacestringnullable‘The space’ section — what's inside the property, how it's laid out.
content.guestAccessstringnullableWhat parts of the property the guest has access to.
content.neighborhoodOverviewstringnullableDescription of the surrounding area.
content.gettingAroundstringnullableTransit, parking, and getting-around notes.
content.transitstringnullablePublic transit specifics, where applicable.
content.houseRulesstringnullableHouse rules guests agree to at booking.
content.additionalRulesstringnullableExtra rules beyond the standard set.
content.notesstringnullableFree-form host notes shown on the listing.
content.interactionWithGuestsstringnullableHow and when the host interacts with guests during the stay.
content: null vs field absent
content is returned as null — not omitted. That's deliberate: it tells you the workspace has no copy yet, instead of leaving you guessing whether you forgot the include. If you don't pass ?include=content at all, the field is absent from the response.include=details
Adds a detailsobject with the structural and operational fields you'd render on a listing page or pass to a guest pre-arrival.
details.propertyTypestringnullableSpecific property type — e.g. ‘Condominium’, ‘Cabin’, ‘Townhouse’.
details.propertyTypeCategorystringnullableTop-level category — e.g. ‘House’, ‘Apartment’, ‘Unique stay’.
details.roomTypeCategorystringnullableRoom arrangement — ‘Entire place’, ‘Private room’, ‘Shared room’.
details.bedroomsintegernullableNumber of bedrooms.
details.bathroomsnumbernullableNumber of bathrooms (may be fractional, e.g. 1.5).
details.bedsintegernullableTotal bed count across all bedrooms.
details.personCapacityintegernullableMaximum number of guests.
details.checkInTimeStartstringnullableEarliest check-in time, 24h format (e.g. ‘15:00’).
details.checkInTimeEndstringnullableLatest check-in time, 24h format.
details.checkOutTimestringnullableCheck-out time, 24h format.
details.minNightsintegernullableMinimum stay length in nights.
details.maxNightsintegernullableMaximum stay length in nights.
details.advanceBookingDaysintegernullableHow far in advance guests can book.
details.turnoverDaysintegernullableMandatory gap days between bookings.
details.wifiNetworkstringnullableWi-Fi network name — for use in pre-arrival messages.
details.wifiPasswordstringnullableWi-Fi password — for use in pre-arrival messages.
details.houseManualstringnullableFree-form house manual / welcome book content.
details.directionsstringnullableDirections to the property.
details.propertySizenumbernullableProperty size (square metres or square feet, depending on locale).
details.yearBuiltintegernullableYear the property was built.
details.numberOfFloorsintegernullableTotal floors in the building.
details.listingFloorintegernullableWhich floor the listing is on.
Wi-Fi credentials are sensitive
wifiNetwork and wifiPasswordare intended for back-end use — pre-arrival messages, lock-box codes, host dashboards. Don't render them on a public listing page.Rooms, policies, stay rules, pricing, fees, taxes and photos
Seven more keys give you the rest of the listing in the same call. Each has one shape for every listing, whether it is connected through Airbnb, Booking.com, Vrbo or a PMS such as Guesty, so you can render or redistribute a property without knowing where it came from.
include=rooms
rooms[].typestringRoom kind: bedroom, living_room, full_bathroom, kitchen, …
rooms[].numberintegernullablePosition among rooms of the same type (bedroom 1, 2, …).
rooms[].bedsarrayBeds in the room: [{ type: 'queen_bed', quantity: 1 }].
include=policies
policies.cancellationPolicystringnullableThe listing's cancellation policy, e.g. flexible.
policies.houseRulesstringnullableHouse rules guests agree to.
policies.checkInobject{ method, instructions, from, until }. method is lockbox, smartlock, keypad, doorman, host_greets, building_staff or other.
policies.checkOut.untilstringnullableCheck-out time.
policies.allowsPets / allowsSmoking / allowsEvents / allowsChildren / allowsInfantsbooleannullableGuest rules.
policies.quietHoursobjectnullable{ start, end } when set.
policies.securityDepositnumbernullableIn the listing currency.
include=rules
rules.minNights / maxNightsintegernullableStay length limits.
rules.bookingWindowDaysintegernullableHow far ahead a guest can book; null when unlimited.
rules.advanceNoticeHoursintegernullableNotice required before check-in.
rules.preparationDaysintegernullableNights blocked between stays.
rules.allowsBookingRequestsbooleannullableWhether guests may send a request inside the notice window.
include=pricing
pricing.currencystringnullableISO currency of every amount on the listing.
pricing.basePrice / weekendPricenumbernullableStanding nightly rates. Per-date rates are on GET /v1/availability/{propertyId}.
pricing.cleaningFee / extraGuestFee / securityDepositnumbernullableStanding fees.
pricing.weeklyDiscountPercent / monthlyDiscountPercentnumbernullablePercent off: 10 means 10%.
include=fees and include=taxes
Every fee (the cleaning fee included) and every tax charged to the guest, in one shape whatever the source — an Airbnb listing's pass-through fees and taxes, or a PMS account's VAT and add-on fees. An empty list means none are set.
fees[].type / namestringcleaning, pet, linen, resort, … and the source's own label, e.g. 'Damage Waiver'.
fees[].amount / amountTypenumber / stringflat in the listing currency, or percent.
fees[].chargedPerstringstay, night, guest or guest_night.
fees[].optionalbooleanAn add-on the guest can choose, rather than always charged.
taxes[].type / name / amount / amountType / chargedPermixedSame fields as fees, e.g. VAT 20 percent per stay.
taxes[].appliesTostring[]nullableWhat the tax is charged on: accommodation, cleaning, other fee types. null means the whole stay.
taxes[].sourcestringairbnb (host remits), airbnb_collected (Airbnb collects and remits), guesty, …
include=photos
The listing's photos in display order: { url, thumbnailUrl, caption, category, width, height, sortOrder }.
curl 'https://api.repull.dev/v1/listings/6248?include=rooms,policies,rules,pricing,fees,taxes' \
-H "Authorization: Bearer sk_live_YOUR_KEY"
{
"id": "6248",
"rooms": [{ "type": "bedroom", "number": 1, "isPrivate": null, "name": null, "beds": [{ "type": "king_bed", "quantity": 1 }] }],
"rules": { "minNights": 2, "maxNights": 1125, "bookingWindowDays": 270, "advanceNoticeHours": 24, "preparationDays": 0, "allowsBookingRequests": true, "instantBook": null },
"pricing": { "currency": "GBP", "basePrice": 95, "weekendPrice": null, "cleaningFee": 110, "weeklyDiscountPercent": 10, "monthlyDiscountPercent": 20 },
"fees": [{ "type": "cleaning", "name": "Cleaning fee", "amount": 110, "amountType": "flat", "chargedPer": "stay", "optional": false, "source": "guesty" }],
"taxes": [{ "type": "vat", "name": "VAT", "amount": 20, "amountType": "percent", "chargedPer": "stay", "appliesTo": ["accommodation", "cleaning"], "included": false, "source": "guesty" }],
"policies": { "cancellationPolicy": "flexible", "checkIn": { "method": "lockbox", "from": "15:00" } }
}All seven also work on GET /v1/listings, read for the whole page at once.
Fetch a listing with both expansions
/v1/listings/{id}?include=content,detailscurl 'https://api.repull.dev/v1/listings/6248?include=content,details' \ -H "Authorization: Bearer sk_live_YOUR_KEY"
Response shape
{
"data": {
"id": "6248",
"name": "Oceanview Villa",
"publicName": "Stunning Oceanview Villa — Private Pool & Beach Access",
"status": "ACTIVE",
"content": {
"summary": "Modern 3-bed villa with ocean views and a private pool.",
"description": "Wake up to the sound of waves...",
"space": "Open-plan living/dining/kitchen on the main floor...",
"guestAccess": "You have full access to the entire villa, the pool deck, and the private beach path.",
"neighborhoodOverview": "Quiet residential street, 5 minutes' walk from the beach...",
"gettingAround": "A car is recommended. Free off-street parking for two vehicles.",
"transit": null,
"houseRules": "No parties. Quiet hours 22:00–08:00.",
"additionalRules": "No smoking anywhere on the property.",
"notes": null,
"interactionWithGuests": "I'm reachable any time via the Repull app and respond within an hour."
},
"details": {
"propertyType": "Villa",
"propertyTypeCategory": "House",
"roomTypeCategory": "Entire place",
"bedrooms": 3,
"bathrooms": 2.5,
"beds": 4,
"personCapacity": 8,
"checkInTimeStart": "15:00",
"checkInTimeEnd": "22:00",
"checkOutTime": "11:00",
"minNights": 2,
"maxNights": 30,
"advanceBookingDays": 365,
"turnoverDays": 1,
"wifiNetwork": "VillaGuest",
"wifiPassword": "beach2026",
"houseManual": "Welcome! Trash collection is Tuesday morning...",
"directions": "From PCH, turn left onto Beach Rd...",
"propertySize": 220,
"yearBuilt": 2014,
"numberOfFloors": 2,
"listingFloor": 1
}
}
}SDK examples
// The SDK's listings.get() / listings.list() do not take `include`,
// so request the expansions directly.
const headers = { Authorization: `Bearer ${process.env.REPULL_API_KEY}` }
const listing = await fetch(
'https://api.repull.dev/v1/listings/6248?include=content,details',
{ headers },
).then((r) => r.json())
console.log(listing.content?.description)
console.log(`${listing.details?.bedrooms} bed / ${listing.details?.bathrooms} bath`)
console.log(`Check-in ${listing.details?.checkInTimeStart}–${listing.details?.checkInTimeEnd}`)
// Or list listings with both expansions
const { data } = await fetch(
'https://api.repull.dev/v1/listings?include=content,details&limit=50',
{ headers },
).then((r) => r.json())
for (const item of data) {
console.log(item.publicName, '—', item.details?.personCapacity, 'guests')
}Combining with ?include=amenities
include is multi-value — pass any combination of amenities, content, details, rooms, policies, rules, pricing, fees, taxes and photos as a comma-separated list. The response merges all requested expansions onto each listing.
curl 'https://api.repull.dev/v1/listings/6248?include=amenities,content,details' \ -H "Authorization: Bearer sk_live_YOUR_KEY"
Pass exactly the keys your view needs — if a particular page only shows the description and bed count, ask for content,details and skip amenities. Unused expansions still cost a few extra fields per listing on the wire.
null vs missing field
The two states mean different things and your code should treat them differently:
| State | Means |
|---|---|
content: {...} | You asked for ?include=content and the listing has copy synced. Individual sub-fields can still be null if that section was never filled in. |
content: null | You asked for ?include=content, but no description row exists for this listing yet (e.g. the listing was just created and hasn't been pushed to a channel). |
content not present | You did not pass ?include=content. The expansion is opt-in. |
The same rule applies to details. Treat nullas “asked, no data” and missing as “didn't ask”.
Unknown include values return 422
Anything other than the keys above is rejected at the edge with a structured error envelope. The response tells you exactly what to change — copy the fix message into a log line and your callers will know what to do.
curl 'https://api.repull.dev/v1/listings/6248?include=thumbnails' \
-H "Authorization: Bearer sk_live_YOUR_KEY"
# HTTP/1.1 422 Unprocessable Entity
{
"code": "invalid_params",
"fix": "Supported values: amenities, content, details, rooms, policies, rules, pricing, fees, taxes, photos. Pass multiple comma-separated, e.g. `?include=amenities`.",
"valid_values": ["amenities", "content", "details", "rooms", "policies", "rules", "pricing", "fees", "taxes", "photos"]
}See errors/invalid_params for the general error contract. The fixfield is human-readable and stable — safe to surface verbatim to a developer or LLM agent.
Related
- List Properties — the base catalog endpoint these expansions hang off.
- Get Property Details — the single-listing fetch.
- errors/invalid_params — full error envelope reference.