Skip to main content
The most common use of the listings API is building a custom landing page or storefront: pull specific collections of a brand’s listings based on your design needs. All of it runs on Get all listings and Get featured listings.

​
Fetch listings

Each item carries what a listing card needs: title, coverMedia, startingPrice and brandCurrency, kind, category, vibes, location, and firstAvailableDate. Responses are paginated (meta + links), 10 items per page by default. For a hero row or curated carousel, Get featured listings returns the listings the brand marked featured, already in the order configured in the dashboard:

​
Filtering

Combine query parameters to build themed collections:

​
Sorting

sortBy accepts title, category, createdAt, status, or listingOrder (the merchandising order the brand arranged in the dashboard - usually the right default for storefronts), with sortDir=ASC|DESC:

​
From card to detail page

When the guest clicks a listing, load its full record with Get a listing - descriptions, media gallery, price tiers, resource groups, cancellation policies, and the kind/experienceId values that drive the booking flow.
Listing data changes rarely - it’s a good candidate for short-lived caching on your side. Availability is what changes constantly; fetch it live via the sessions endpoints.