# Otodom Agency Profile Scraper (`scrapyx/otodom-agency-profile-scraper`) Actor

Looks up Otodom real-estate agency and developer accounts by id and returns their bio, contact info, website, location, quality badges and true active-listing count, straight from the account's own public profile page.

- **URL**: https://apify.com/scrapyx/otodom-agency-profile-scraper.md
- **Developed by:** [Ibnu Adzim](https://apify.com/scrapyx) (community)
- **Categories:** Real estate, Lead generation, Business
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.26 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
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?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Otodom Agency Profile Scraper

Looks up **[Otodom](https://www.otodom.pl)** (Poland's #1 property portal,
OLX Group) real-estate agency and developer accounts by id and returns
their bio, contact info, website, location, quality badges and **true
active-listing count** — straight from the account's own public profile
page.

Sibling to `properties/otodom-properties-scraper` (property listing
search) in this portfolio — that actor's own build notes flagged this gap
explicitly: agency/developer profile data is a different data-type for a
different audience (agency intelligence — prospecting, lead lists,
competitor research — not property search), worth its own actor rather
than bolted onto the listing scraper.

Public data only. No login, no cookies, no browser.

### How this works

Every agency or developer on Otodom has a public profile page at
`otodom.pl/pl/firmy/biura-nieruchomosci/ID{accountId}` — the exact same
`accountId` already present on every listing row the sibling actor
produces for an agency/developer-owned property (`ad.agency.id` /
`ad.owner.id`). This actor fetches that page and reads its embedded
`__NEXT_DATA__` (the same Next.js SSR mechanism the sibling actor uses),
which carries a much richer profile than what shows up in a listing
search: full bio text, website, member-since date, and a true
active-listing count broken down by sell/rent/investment.

**There is no "search agencies by name" mode.** The only public entry
point is this numeric id, so the natural workflow is: run
`otodom-properties-scraper`, collect the agency/developer ids from its
output, feed them here. Same "opaque id only" shape this portfolio already
accepted for `property24-properties-scraper`.

### What you get

Two record types share one dataset, told apart by `recordType`.

#### `AGENCY` — one row per account

`accountName`, `accountType` (`AGENCY` or `DEVELOPER`), `accountDescription`
(free-text bio), `accountWebsite`, `accountPhone`/`accountAlternativePhone`,
`locationFullName`/`locationAddress`/`locationPostalCode`, `sellerBadges`
(reputation badges — there is no numeric star rating on this platform),
`memberSince`, and the listing counts: `activeAdsTotal` (true total across
the account's whole catalogue) plus `activeSellAds`/`activeRentAds`/
`activeInvestmentAds`/`citiesWithAds`.

Also includes `previewAds` / `previewAdsCount` — a **small, capped
preview** of the account's ads (confirmed capped at 6 regardless of
`activeAdsTotal`; see "Known limits"). Never conflated with the true
total.

#### `ERROR` — one row per id that failed to resolve

Unknown id, transport failure, or an unrecognised page shape.

### Input

| Field | What it does |
| --- | --- |
| **Agency / developer account ids** | numeric Otodom account ids — e.g. `134199` (also accepts `ID134199`) |

#### Example

```json
{
  "accountIds": ["134199", "10556423"]
}
```

### Notes on reliability

- Otodom loads a DataDome tag on every page, but no challenge was observed
  cold on this surface across the full TLS profile pool — same posture as
  the sibling actor.
- A wrong or made-up account id answers a clean HTTP 404, not a redirect
  to search/home and not a differently-shaped "not found" page.
- The slug text in front of `ID{accountId}` in the URL is purely
  cosmetic — confirmed live with both a wrong slug and no slug at all,
  both resolving to the exact same canonical page.
- Residential proxy, no country pin, is the cloud default.

### Known limits

- **No "search agencies" mode.** You need account ids from elsewhere
  (this portfolio's own `otodom-properties-scraper` output, or an Otodom
  URL you already have) — there is no name/city lookup.
- **`previewAds` is a fixed preview widget, not the full catalogue.**
  Verified directly: every `page`/`offset`/`limit` query-parameter variant
  tried against the profile page returns the identical 6 ads regardless
  of the account's true `activeAdsTotal` (observed as high as 548). If you
  need the account's full listing inventory, cross-reference
  `otodom-properties-scraper`'s own search output by `agency.id`/`owner.id`
  instead of relying on this preview.
- **Private (individual) sellers have no profile page at all** and are
  out of scope by construction — their listings carry no `agency` object
  to look up in the first place.

# Actor input Schema

## `accountIds` (type: `array`):

Numeric Otodom account ids, e.g. `134199` (also accepts `ID134199`). Get these from ad.agency.id / ad.owner.id in otodom-properties-scraper's own output — there is no 'search agencies by name' mode, this actor only works through ids you already have.

## `maxConcurrency` (type: `integer`):

Upper bound on requests in flight at once, across all account ids.

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

Otodom loads a DataDome tag but no challenge was observed cold on this surface across the TLS profile pool. Residential is still the cloud default as this portfolio's standard baseline.

## Actor input object example

```json
{
  "accountIds": [
    "134199"
  ],
  "maxConcurrency": 6,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}
```

# Actor output Schema

## `items` (type: `string`):

One row per scraped record. See the dataset's default view for field definitions.

# 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 = {
    "accountIds": [
        "134199"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("scrapyx/otodom-agency-profile-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 = { "accountIds": ["134199"] }

# Run the Actor and wait for it to finish
run = client.actor("scrapyx/otodom-agency-profile-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 '{
  "accountIds": [
    "134199"
  ]
}' |
apify call scrapyx/otodom-agency-profile-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,scrapyx/otodom-agency-profile-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/Tbe8IISvAdnKht7CV/builds/QdLJDEojpZThnq1vK/openapi.json