Otodom Agency Profile Scraper

Looks up Otodom (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

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