# Traveloka Indonesia Lodging & Xperience Articles (`nimbryxo-studio/traveloka-indonesia-lodging-and-xperience-articles`) Actor

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.

- **URL**: https://apify.com/nimbryxo-studio/traveloka-indonesia-lodging-and-xperience-articles.md
- **Developed by:** [Nimbryxo-studio](https://apify.com/nimbryxo-studio) (community)
- **Categories:** Travel, Automation, News
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.49 / 1,000 results

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Traveloka Indonesia Lodging & Xperience Articles

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

| Field | Type | Default | Description |
|---|---|---|---|
| `mode` | string | `search` | `search` / `browseByCity` / `browseExplore` / `byUrl` |
| `searchQuery` | string | `yogyakarta` | City, area or guide keyword (mode=search) |
| `citySlug` | string | – | 21 verified city/area listing pages (mode=browseByCity) |
| `startUrls` | array | `[]` | Traveloka listing, category or article URLs (mode=byUrl) |
| `locale` | string | `en-id` | Storefront and price currency |
| `exploreCategory` | string | `activities` | `activities` / `tips` (mode=browseExplore) |
| `exploreSubcategory` | string | – | Activities sub-category, blank for all (mode=browseExplore) |
| `minRating` | int | – | Minimum guest score (1–10) |
| `minStarRating` | int | – | Minimum star rating (1–7) |
| `minReviewCount` | int | – | Minimum number of reviews |
| `minPrice` | int | – | Minimum listed price in the locale currency |
| `maxPrice` | int | – | Maximum listed price in the locale currency |
| `containsKeyword` | string | – | Only hotels whose name contains this text |
| `sortBy` | string | `relevance` | `relevance` / `ratingDesc` / `mostReviewed` / `starDesc` / `priceAsc` / `priceDesc` |
| `includeArticles` | boolean | `false` | In search mode, emit all fetched articles, not just keyword matches |
| `includeArticleDetails` | boolean | `false` | Open each article page for full body text, description, TOC and related reads |
| `includeHotelDetails` | boolean | `false` | Fetch each hotel's cookieless detail data: address, coordinates, facilities, check-in/out, policies and up to 20 reviews |
| `maxPages` | int | `0` | Pages per source; `0` = all until `maxItems` or exhaustion (0–500) |
| `maxItems` | int | `50` | Hard record cap (1–1000) |
| `proxyConfiguration` | object | – | 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

```json
{
  "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

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

#### Example: page through Activities guides

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

#### Example: scrape specific pages

```json
{
  "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.

# Actor input Schema

## `mode` (type: `string`):

What to fetch.

## `searchQuery` (type: `string`):

City, area, or travel keyword (mode=search), e.g. `yogyakarta`, `bali`, `hotel bali`, `train`. City/area queries return accommodation listings; other keywords match Traveloka Xperience article titles and summaries.

## `citySlug` (type: `string`):

Traveloka accommodation listing page to scrape (mode=browseByCity). All pages are paginated automatically up to `maxPages`.

## `startUrls` (type: `array`):

Traveloka URLs to scrape (mode=byUrl): accommodation listing pages, explore category pages, or explore article pages. Listing pages are paginated automatically.

## `locale` (type: `string`):

Traveloka store locale. The locale also sets the price currency shown on listing pages (e.g. `en-sg` → SGD).

## `exploreCategory` (type: `string`):

Traveloka Explore category to page through (mode=browseExplore).

## `exploreSubcategory` (type: `string`):

Optional Activities sub-category filter (mode=browseExplore with `exploreCategory=activities`).

## `minRating` (type: `integer`):

Only hotels with a guest score of at least this (Traveloka uses a 0–10 scale).

## `minStarRating` (type: `integer`):

Only hotels with at least this many stars.

## `minReviewCount` (type: `integer`):

Only hotels with at least this many guest reviews.

## `minPrice` (type: `integer`):

Only hotels whose listed starting price is at least this amount, in the locale's currency (see `locale`).

## `maxPrice` (type: `integer`):

Only hotels whose listed starting price is at most this amount, in the locale's currency (see `locale`).

## `containsKeyword` (type: `string`):

Only emit hotels whose name contains this text (case-insensitive).

## `sortBy` (type: `string`):

Applied to the fetched hotel records before the output cap. `relevance` keeps Traveloka's own popularity order.

## `includeArticles` (type: `boolean`):

In search mode, also emit every article from the fetched Explore pages, not only keyword matches.

## `includeArticleDetails` (type: `boolean`):

Also open each article page to add the full body text, section headings and images, plus description, table of contents and related articles. Adds one request per article.

## `includeHotelDetails` (type: `boolean`):

Also fetch each hotel's cookieless detail data to add address, coordinates, facilities, check-in/out, policies and up to 20 reviews. Adds one request per hotel.

## `maxPages` (type: `integer`):

Maximum listing/category pages to fetch per source. `0` means all pages until `maxItems` or the source is exhausted.

## `maxItems` (type: `integer`):

Hard cap on emitted records.

## `query` (type: `string`):

Deprecated alias for `searchQuery`.

## `keyword` (type: `string`):

Deprecated alias for `searchQuery`.

## `q` (type: `string`):

Deprecated alias for `searchQuery`.

## `location` (type: `string`):

Deprecated alias for `searchQuery`.

## `city` (type: `string`):

Deprecated alias for `citySlug`.

## `maxResults` (type: `integer`):

Deprecated alias for `maxItems`.

## `limit` (type: `integer`):

Deprecated alias for `maxItems`.

## `sort` (type: `string`):

Deprecated alias for `sortBy`.

## `url` (type: `string`):

Deprecated single-URL alias for `startUrls`.

## `proxyConfiguration` (type: `object`):

Optional Apify proxy. Only used after a direct request is blocked (403/429). Leave empty for the zero-cost default.

## Actor input object example

```json
{
  "mode": "browseExplore",
  "searchQuery": "yogyakarta",
  "startUrls": [],
  "locale": "en-id",
  "exploreCategory": "activities",
  "exploreSubcategory": "",
  "sortBy": "relevance",
  "includeArticles": false,
  "includeArticleDetails": false,
  "includeHotelDetails": false,
  "maxPages": 1,
  "maxItems": 3,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

## `hotels` (type: `string`):

Dataset containing all scraped Traveloka records.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "mode": "browseExplore",
    "searchQuery": "yogyakarta",
    "startUrls": [],
    "locale": "en-id",
    "exploreCategory": "activities",
    "exploreSubcategory": "",
    "sortBy": "relevance",
    "includeArticles": false,
    "includeArticleDetails": false,
    "includeHotelDetails": false,
    "maxPages": 1,
    "maxItems": 3,
    "proxyConfiguration": {
        "useApifyProxy": false
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("nimbryxo-studio/traveloka-indonesia-lodging-and-xperience-articles").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "mode": "browseExplore",
    "searchQuery": "yogyakarta",
    "startUrls": [],
    "locale": "en-id",
    "exploreCategory": "activities",
    "exploreSubcategory": "",
    "sortBy": "relevance",
    "includeArticles": False,
    "includeArticleDetails": False,
    "includeHotelDetails": False,
    "maxPages": 1,
    "maxItems": 3,
    "proxyConfiguration": { "useApifyProxy": False },
}

# Run the Actor and wait for it to finish
run = client.actor("nimbryxo-studio/traveloka-indonesia-lodging-and-xperience-articles").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "mode": "browseExplore",
  "searchQuery": "yogyakarta",
  "startUrls": [],
  "locale": "en-id",
  "exploreCategory": "activities",
  "exploreSubcategory": "",
  "sortBy": "relevance",
  "includeArticles": false,
  "includeArticleDetails": false,
  "includeHotelDetails": false,
  "maxPages": 1,
  "maxItems": 3,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}' |
apify call nimbryxo-studio/traveloka-indonesia-lodging-and-xperience-articles --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,nimbryxo-studio/traveloka-indonesia-lodging-and-xperience-articles"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/VavynKRzqGjI2llPF/builds/fXSHrRLVZSK3zwWRR/openapi.json
