# OLX Product Search Scraper (`w3crawler/olx-product-search-scraper`) Actor

Search and scrape classified product listings from OLX across multiple country domains. Supports keyword search, category filtering, location, and sort order. Extracts title, price, location, seller name, and listing URL — ideal for C2C marketplace research and second-hand market analysis.

- **URL**: https://apify.com/w3crawler/olx-product-search-scraper.md
- **Developed by:** [w3crawler](https://apify.com/w3crawler) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.99 / 1,000 product search results

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

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

## OLX Product Search Scraper

Scrape product listings from public OLX pages across multiple countries using bounded, browser-compatible HTML requests and JSON-LD/card parsing. It does not use login, private APIs, or CAPTCHA bypass.

### Features

- **Multi-country support** — scrape `olx.pl`, `olx.pt`, `olx.ro`, `olx.bg`, `olx.ua`, `olx.kz`, `olx.in`, and more
- **Keyword search** — find listings by product name or category keyword
- **Compatible inputs** — accepts legacy category, location, and sort fields while using the selected public URL or current country search route
- **Configurable result limit** — set `maxItems` to control how many listings to collect
- **Cloud-ready** — runs on Apify with scheduling, optional standard proxy configuration, and webhook support

### Use Cases

- Cross-country price comparison for second-hand goods
- Market research on buyer demand and listing volumes
- Competitor monitoring for classified ad sellers
- Automated inventory and pricing alerts

### Input

| Field | Type | Default | Required | Description |
|-------|------|---------|----------|-------------|
| `domain` | string | `olx.pl` | | OLX country domain, e.g. `olx.pl`, `olx.in`, `olx.ro` |
| `query` | string | `—` | | Keyword to search for (e.g. "laptop", "phone", "furniture") |
| `categoryId` | integer | `—` | | OLX category numeric ID (optional filter). Varies by country |
| `location` | string | `—` | | Optional public location slug used when no query is supplied |
| `sortBy` | string | `created_at:desc` | | Compatibility preference retained in run input and output context |
| `maxItems` | integer | `50` | | Maximum number of listings to scrape |
| `maxPages` | integer | `1` | | Bounded number of page variants requested per source URL |
| `proxyConfiguration` | object | direct | | Optional standard Apify Proxy settings; enabled runs reuse one valid session ID and never expose credentials in output |

#### Example Input

```json
{
  "domain": "olx.pl",
  "query": "laptop",
  "sortBy": "created_at:desc",
  "maxItems": 25,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

### Output

Each scraped listing includes:

| Field | Description |
|-------|-------------|
| `productName` | Listing title |
| `price` | Price as displayed (e.g. "3 500 zł") |
| `location` | City or region of the listing |
| `listingUrl` | Direct URL to the OLX listing |
| `postedAt` | Date the ad was posted |
| `productDescription` | Short listing description when public structured data provides it |
| `category` | Category name |
| `query` | Search keyword used |
| `listingId` | OLX internal listing ID |
| `scrapedAt` | ISO timestamp when the listing was scraped |

### Notes

- Public page structure and access controls vary by country. Blocked pages produce diagnostic rows; the Actor does not bypass access controls.
- `categoryId` values differ by country — check the public OLX category URL for your domain.

`categoryId` and `sortBy` are applied to the public search URL, and `location` participates in the search route. With `scrapeDetails: true`, the Actor follows each public listing URL once and merges additional structured fields while retaining the bounded global item limit.

You can download the dataset in various formats such as JSON, HTML, CSV, or Excel. `requestDelayMs`, `maxRequestRetries`, and `fixturePath` provide bounded retry pacing and explicit checked-in local QA without silently replacing live access.

# Changelog

This Actor's version history is a separate document: https://apify.com/w3crawler/olx-product-search-scraper/changelog.md

# Actor input Schema

## `domain` (type: `string`):

Supported OLX country domain, such as olx.pl, olx.pt, olx.ro, olx.ua, olx.kz, or olx.in.

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

Keyword used to build a public OLX search URL.

## `categoryId` (type: `integer`):

Optional public OLX category filter added as search\[category\_id].

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

Optional location used when constructing a public search URL.

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

Public OLX search\[order] preference.

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

Maximum unique listing records.

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

Bounded number of page variants requested per source URL.

## `scrapeDetails` (type: `boolean`):

Fetch each public listing page once and merge additional structured fields when available.

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

Optional standard Apify Proxy settings. Direct public HTTP is the default; enabled runs reuse one consistent session and do not bypass access controls.

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

Optional public HTTPS OLX URLs. When omitted, a search URL is built from domain, query, and location.

## `timeoutMs` (type: `integer`):

Maximum time per public request.

## `maxBytes` (type: `integer`):

Maximum bytes read per public response.

## `requestDelayMs` (type: `integer`):

Bounded delay before retrying a failed public request.

## `maxRequestRetries` (type: `integer`):

Bounded retries for transient or access-boundary responses.

## `fixturePath` (type: `string`):

Optional checked-in HTML/JSON/TXT fixture path for deterministic local QA; never used as a live fallback.

## Actor input object example

```json
{
  "domain": "olx.pl",
  "sortBy": "created_at:desc",
  "maxItems": 50,
  "maxPages": 1,
  "scrapeDetails": false,
  "proxyConfiguration": {
    "useApifyProxy": false
  },
  "timeoutMs": 30000,
  "maxBytes": 5000000,
  "requestDelayMs": 250,
  "maxRequestRetries": 1
}
```

# Actor output Schema

## `dataset` (type: `string`):

No description

## `keyValueStore` (type: `string`):

No description

## `runSummary` (type: `string`):

No description

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("w3crawler/olx-product-search-scraper").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("w3crawler/olx-product-search-scraper").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 '{}' |
apify call w3crawler/olx-product-search-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,w3crawler/olx-product-search-scraper"
        }
    }
}
```

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/DIA10x8e9LNexpbiT/builds/LIKsy8wZ36umCOgxR/openapi.json