Traveloka Indonesia Lodging & Xperience Articles avatar

Traveloka Indonesia Lodging & Xperience Articles

Pricing

from $0.49 / 1,000 results

Go to Apify Store
Traveloka Indonesia Lodging & Xperience Articles

Traveloka Indonesia Lodging & Xperience Articles

Get guest house and hostel listings across Indonesia's major cities and resort areas with ratings and reviews, plus Traveloka Xperience travel-guide articles with author, publish date, and full article text.

Pricing

from $0.49 / 1,000 results

Rating

0.0

(0)

Developer

Nimbryxo-studio

Nimbryxo-studio

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

9 hours ago

Last modified

Features

Limited permissions

Share

Traveloka is Southeast Asia's largest travel booking platform, and its Indonesian accommodation pages expose a rich, server-rendered catalogue: guest houses, hostels, hotels, nightly starting prices, guest scores, review counts, amenities and photo galleries. This actor collects that catalogue city by city, follows every listing page to the end, and can switch between Traveloka's regional storefronts and currencies. It can optionally enrich each hotel with address, coordinates, facilities, check-in policies and up to 20 recent reviews. It also pages through the Traveloka Xperience content hub, returning travel-guide articles with authors, publish dates, reading times, full body text, images and related reads. No login, cookies or proxy setup required.

What this actor does

  • Four ways in: search, browseByCity, browseExplore, byUrl
  • Paginated listings: walks /accommodation/find/<slug>, /2, /3… until Traveloka's own result count, so a city query can return hundreds of properties instead of the first 21
  • Six storefronts: en-id, id-id, en-sg, en-my, th-th, en-ph, with the matching currency on every price
  • Article hub: category pages (activities, tips), Activities sub-categories, and optional article-detail enrichment
  • Optional hotel details: address, coordinates, facilities, check-in/out, policies and up to 20 recent reviews
  • Filters: guest score, star rating, review count, price range, keyword in name, and six sort orders
  • Clean records: empty values are omitted at every depth, never written as null

Output per hotel

  • hotelId — Traveloka property ID
  • name, displayName, location — name and area/city
  • starRating, userRating (0–10), numReviews, userRatingInfo
  • accommodationType, travelTheme, hotelFeatures[]
  • price, baseFare, taxes, fees — listed starting rate for the locale's default stay window
  • priceCurrency — ISO currency of the listing page (IDR, SGD, MYR, THB, PHP)
  • highlightedReview, reviewerName, highlightedReviewTranslated — translation marker only when Traveloka supplies it
  • urgencyMessage — Traveloka's demand label when shown (e.g. "Often fully booked!")
  • seoPath, seoPathType, hotelUrl
  • images[], imageUrl, thumbnailUrl, imageCount
  • mainImageUrl, mainImageCaption — the asset Traveloka marks as the main photo, and its caption
  • imageCategories[] — distinct asset categories shown for the property
  • ribbonLabel, preferredPartner — Traveloka merchandising labels when shown
  • locale — storefront used for this record
  • sourceUrl — the listing page the record came from
  • With includeHotelDetails: address, postalCode, city, province, country, latitude, longitude
  • With includeHotelDetails: facilityCategories[] (category, items[]), facilities[], checkInTime, checkOutTime
  • With includeHotelDetails: policies[] (title, description, type), checkInInstructions, importantNotice
  • With includeHotelDetails: hotelReviews[] — up to 20 rows with reviewId, score, maxScore, text, originalText, reviewerId, reviewerName, reviewerPhotoUrl, reviewerStatus, timestamp, ownerReply, media[], subRatings[], reviewOrigin, reviewProvider, translationStatus
  • recordType: "hotel", scrapedAt

Output per article

  • articleId, title, subtitle, description, articleUrl
  • authorName, authorPicture, publishedDate, readingTimeSec
  • imageUrl, tags[], shareLink, locale
  • With includeArticleDetails: modifiedAt, shareCount, articleType, contentType, authorGroup, imageCount, wordCount, readDuration, headerImage, headerImages[], subCategories[], tocSections[], and relatedArticles[] (articleId, title, articleUrl, publishedDate, readDuration, imageUrl)
  • With includeArticleDetails: articleBody (plain text), articleSections[] (each section has optional title plus paragraphs[]), and articleImages[] (deduplicated absolute URLs); promo cards, carousels and deep-link buttons are skipped
  • recordType: "article", scrapedAt

Input

FieldTypeDefaultDescription
modestringsearchsearch / browseByCity / browseExplore / byUrl
searchQuerystringyogyakartaCity, area or guide keyword (mode=search)
citySlugstring–21 verified city/area listing pages (mode=browseByCity)
startUrlsarray[]Traveloka listing, category or article URLs (mode=byUrl)
localestringen-idStorefront and price currency
exploreCategorystringactivitiesactivities / tips (mode=browseExplore)
exploreSubcategorystring–Activities sub-category, blank for all (mode=browseExplore)
minRatingint–Minimum guest score (1–10)
minStarRatingint–Minimum star rating (1–7)
minReviewCountint–Minimum number of reviews
minPriceint–Minimum listed price in the locale currency
maxPriceint–Maximum listed price in the locale currency
containsKeywordstring–Only hotels whose name contains this text
sortBystringrelevancerelevance / ratingDesc / mostReviewed / starDesc / priceAsc / priceDesc
includeArticlesbooleanfalseIn search mode, emit all fetched articles, not just keyword matches
includeArticleDetailsbooleanfalseOpen each article page for full body text, description, TOC and related reads
includeHotelDetailsbooleanfalseFetch each hotel's cookieless detail data: address, coordinates, facilities, check-in/out, policies and up to 20 reviews
maxPagesint0Pages per source; 0 = all until maxItems or exhaustion (0–500)
maxItemsint50Hard record cap (1–1000)
proxyConfigurationobject–Optional; only used after a direct request is blocked

Legacy saved-task aliases are accepted but hidden from the form: query, keyword, q, location, city, maxResults, limit, sort, and url.

Examples

Example: paginated guest houses in Bali

{
"mode": "browseByCity",
"citySlug": "guest-house-bali",
"locale": "en-id",
"minRating": 8,
"sortBy": "ratingDesc",
"maxPages": 5,
"maxItems": 100
}

Example: Singapore-dollar prices for a budget shortlist

{
"mode": "browseByCity",
"citySlug": "guest-house-yogyakarta",
"locale": "en-sg",
"maxPrice": 60,
"sortBy": "priceAsc",
"maxItems": 40
}

Example: page through Activities guides

{
"mode": "browseExplore",
"exploreCategory": "activities",
"exploreSubcategory": "nature-wildlife",
"includeArticleDetails": true,
"maxPages": 3,
"maxItems": 25
}

Example: scrape specific pages

{
"mode": "byUrl",
"startUrls": [
{"url": "https://www.traveloka.com/en-id/accommodation/find/hostel-bali"},
{"url": "https://www.traveloka.com/en-id/explore/activities/luxury-train-journeys-for-senior-couple/1009917"}
]
}

Data source and limits

The actor reads the same server-rendered accommodation-listing and Explore pages that Traveloka serves to search engines and visitors without an account. Listing prices are the indicative starting rates shown for each property's default stay window, not a quote for dates you choose; checking live room availability happens in Traveloka's own checkout flow. With includeHotelDetails, the actor uses the cookieless Next data route for each hotel page (the listing page supplies the current buildId) to add address, coordinates, facilities, check-in/out, policies and up to 20 recent reviews. This enrichment is best-effort: if a detail request fails, the hotel record is still emitted from listing data. Date-specific room rates and availability are WAF-gated and are not requested or returned; without includeHotelDetails, only the highlighted review shown on the listing card is returned. Article pages embed their full body in the server-rendered viewDescription layout, so with includeArticleDetails the actor returns articleBody, structured articleSections and articleImages alongside the existing metadata, TOC and related reads.

Traveloka paginates its listing and Explore category pages. The actor follows those pages until Traveloka's reported total is reached, maxPages stops it, or maxItems is full. Sorting and the rating/price/keyword filters are applied to the records the actor has fetched (up to maxItems), not to Traveloka's entire result set; raise maxItems or maxPages for a wider pool. A listing that reports a smaller total than you expected is showing what Traveloka itself reports for that city and accommodation type.

Use cases

  • Budget-accommodation mapping — enumerate guest houses and hostels across Indonesian cities, with scores and review volumes
  • Price benchmarking — compare listed starting rates across Traveloka's regional storefronts in local currencies
  • Travel-content research — collect Xperience guides by category, sub-category and author for itinerary or trend analysis
  • Listing monitoring — rerun a city on a schedule to track new properties, rating changes and merchandising labels
  • Data enrichment — join hotel photos, amenities, SEO paths and guest-score labels into an existing property database

FAQ

Is this actor affiliated with Traveloka? No. It is an independent tool that reads Traveloka's public listing and Explore pages.

Why do prices differ between locales? Each storefront shows its own currency: en-id/id-id use IDR, en-sg uses SGD, en-my uses MYR, th-th uses THB and en-ph uses PHP. priceCurrency records the currency, so compare like with like.

Are the prices live quotes for my travel dates? No. They are the starting rates Traveloka advertises on the listing page for its default stay window. Live availability and a final price depend on dates and room selection in Traveloka's booking flow.

Why is a hotel missing a price or a rating? Traveloka does not show a starting rate or guest score for every property in every city. Those fields are left out of the record rather than filled with a guess.

How many records can one run return? maxItems caps a run at 1000 records. Within that cap, maxPages controls how many listing or category pages are read; 0 means read until the source is exhausted.

Can I get both hotels and articles in one search run? Yes. search tries a matching city/area listing first, then article titles and summaries. Set includeArticles to true to keep every fetched article, not just matching ones.

Does the actor return the full article text? Yes, when includeArticleDetails is enabled. Each article detail record carries articleBody as plain text, articleSections[] with optional headings and paragraph blocks, and articleImages[] with deduplicated absolute image URLs. Promotional cards, carousels and booking buttons are excluded.

Does includeHotelDetails return room rates? No. It adds static detail data (address, coordinates, facilities, check-in/out, policies) and up to 20 recent reviews. Date-specific room rates and availability are protected by Traveloka's WAF and are not requested or returned.

What is userRating? Traveloka's own guest-satisfaction score on a 0–10 scale. userRatingInfo is the matching label, such as "Very Good" or "Exceptional".

Do I need to configure a proxy? No. The actor requests Traveloka pages directly by default, then retries through Apify's AUTO datacenter proxy automatically if direct requests are blocked. The optional proxyConfiguration is only needed for a custom proxy.

Why are only some cities in the citySlug dropdown? Those are the listing pages verified to return properties without a login. For any other Traveloka listing URL, use mode=byUrl and paste the URL — pagination is handled for you.

How fresh is the data? Every run reads the live page at run time, so the records reflect what Traveloka is showing at that moment.