PropertyFinder Scraper | Contacts & History

Slug: fatihtahta/propertyfinder-agnets-scraper

Overview

PropertyFinder Agents Scraper collects structured public records for real estate agents and companies on Property Finder UAE, including contact details, profile metadata, broker information, ratings, property counts, locations, and transaction history when available. The actor is designed for the public directory experience at www.propertyfinder.ae/en/find-broker, which is useful for understanding the UAE real estate agent and brokerage landscape; see the public Property Finder UAE website for source context. Results are delivered as repeatable JSON records that can be used in analytics, enrichment, CRM, and monitoring workflows. The actor supports consistent recurring data acquisition by letting teams define a directory type, market scope, and maximum output size. It is intended for dependable operational collection without making assumptions about completeness beyond what is publicly available at run time.

Why Use This Actor

• Market research and analytics teams: build structured extraction workflows for agent coverage, brokerage presence, ratings, locations, property counts, and public transaction signals.
• Product and content teams: normalize directory data for comparison tools, profile indexes, internal catalogs, and content operations.
• Developers and data engineering teams: feed predictable JSON records into downstream systems, ETL jobs, warehouse tables, search indexes, and monitoring workflows.
• Lead generation and enrichment teams: create targeted prospect lists from public agent and company records, then enrich CRM profiles with current public attributes.
• Monitoring and competitive tracking teams: schedule repeatable collection to observe changes in agent activity, company presence, ranking signals, and market coverage over time.

Common Use Cases

• Market intelligence: monitor agent supply, company coverage, ratings, locations, listing counts, and transaction signals across UAE market segments.
• Lead generation: build targeted lists of agents or companies by category, location, and specialization.
• Competitive monitoring: track public profile and company changes across brokerages, agents, ratings, property counts, and visible market activity.
• Catalog and directory building: populate internal databases with structured public agent and brokerage records.
• Data enrichment: add current public contact, broker, language, location, rating, and property-count attributes to CRM, BI, or analytics datasets.
• Recurring reporting: schedule periodic runs for dashboards, operational reports, alerts, and trend analysis.

Quick Start

1. Choose Agents or Companies in category.
2. Add a location when you want to focus on a UAE city, community, neighborhood, or building.
3. For agent runs, set specialization to the segment you want to collect, such as Residential For Sale, Residential For Rent, or Apartment.
4. Set a small limit, such as 10 or 50, for the first validation run.
5. Run the actor in Apify Console and inspect the first dataset records.
6. Increase the limit, broaden or narrow filters, and schedule recurring runs once the output matches your workflow.

Input Parameters

The actor accepts a directory category, optional UAE location, optional agent specialization, and maximum record limit.

Parameter	Type	Description	Default
category	string	Directory type to collect. Allowed values: Agents, Companies. Company searches return company records and do not use specialization.	Agents
location	string	UAE city, community, neighborhood, or building, such as Dubai, Business Bay, Dubai Marina, or Jumeirah Village Circle. Leave empty to search across all locations.	–
specialization	string	Agent segment to collect. Applies only when category is Agents. Accepted examples include Residential For Sale, Residential For Rent, Commercial For Sale, Commercial For Rent, Apartment, Villa, Townhouse, Office Space, Warehouse, Shop, Land, and Penthouse.	Residential For Sale
limit	integer	Maximum number of records to save. Use a small number for validation or sampling; leave blank to continue through the available result set. Minimum: 1.	100

Choosing Inputs

Use category first to decide whether the run should collect individual agent profiles or company records. Add location when you need a focused dataset for a specific UAE market; leave it empty when the goal is broad discovery. For agent runs, use specialization to narrow the profile segment and produce a more targeted dataset. Broader inputs improve discovery, while narrower inputs are better for segmented reporting, enrichment, and monitoring. Start with a small limit to validate record shape and increase it after confirming the data fits your use case.

Example Inputs

Location and specialization run

{
  "category": "Agents",
  "location": "Business Bay",
  "specialization": "Residential For Sale",
  "limit": 50
}

Company discovery run

{
  "category": "Companies",
  "location": "Dubai",
  "limit": 100
}

Broad agent sample

{
  "category": "Agents",
  "specialization": "Apartment",
  "limit": 25
}

Output

9.1 Output destination

The actor writes results to an Apify dataset as JSON records. The dataset is designed for direct consumption by analytics tools, ETL pipelines, and downstream APIs with minimal post-processing.

The actor emits two public record families: agent for individual agent profiles and agency for brokerage/company records. Both use the same normalized envelope: record_type, record_id, source_context, entity, grouped business objects, and fingerprint.

9.2 Record envelope and stable identifiers

Use record_id as the primary idempotency key. It is the strongest Property Finder identifier available for the saved entity and is kept as a string so it can be joined safely across databases, spreadsheets, and APIs. Use entity.url as the public profile URL and fingerprint as a compact comparison key for repeated exports.

source_context captures source identity and collection context such as page index, result position, seed metadata, category, specialization, and search location when available. Direct profile identity stays under entity; contact channels stay under contact_details; broker or agency data stays under brokerage.

9.3 Examples

Example: agent (record_type = "agent")

{
  "record_type": "agent",
  "record_id": "900001",
  "source_context": {
    "source_name": "Property Finder UAE",
    "source_domain": "propertyfinder.ae",
    "page_index": 1,
    "search_position": 1,
    "seed_id": "1c4c8c69a3755d9209ba",
    "seed_type": "search",
    "category": "agents",
    "specialization": "Residential For Sale"
  },
  "entity": {
    "id": "900001",
    "url": "https://www.propertyfinder.ae/en/agent/omar-haddad-900001",
    "slug": "omar-haddad",
    "name": "Omar Haddad",
    "description": "Experienced real estate consultant focused on helping clients evaluate residential investment opportunities.",
    "external_ids": {
      "propertyfinder_agent_id": "900001",
      "propertyfinder_user_id": "700001"
    }
  },
  "agent": {
    "user_id": "700001",
    "position": "Sales Specialist",
    "bio": "Experienced real estate consultant focused on helping clients evaluate residential investment opportunities.",
    "nationality": {
      "code": "AE",
      "name": "United Arab Emirates"
    },
    "license_number": "900001",
    "linkedin": "https://www.linkedin.com/in/example-agent",
    "is_superagent": true,
    "is_verified": true,
    "experience_since": 2024
  },
  "brokerage": {
    "id": "5001",
    "client_id": "5001",
    "slug": "example-prime-real-estate-5001",
    "name": "Example Prime Real Estate LLC",
    "address": "Office 1204, Example Business Tower, Business Bay, Dubai, United Arab Emirates",
    "location": "Dubai",
    "logo": {
      "url": "https://static.shared.propertyfinder.ae/media/images/client_logos/5001/example-logo/260x200.jpg",
      "token": "examplelogotoken0000000000000000000000",
      "path": "/media/images/client_logos/5001/example-logo/original.png",
      "links": {
        "desktop": "https://static.shared.propertyfinder.ae/media/images/client_logos/5001/example-logo/260x200.jpg",
        "mobile": "https://static.shared.propertyfinder.ae/media/images/client_logos/5001/example-logo/130x100.jpg"
      }
    }
  },
  "contact_details": {
    "email": "omar.haddad@example.com",
    "phone": "+971500000000",
    "whatsapp_phone": "+971500000000"
  },
  "media": {
    "profile_image": {
      "url": "https://www.propertyfinder.ae/agent/0/260/200/MODE/example/900001-profile.jpg?ctr=ae",
      "path": "900001/profile.jpg",
      "links": {
        "agentCard": "https://www.propertyfinder.ae/agent/0/170/200/MODE/example/900001-profile.jpg?ctr=ae",
        "desktop": "https://www.propertyfinder.ae/agent/0/260/200/MODE/example/900001-profile.jpg?ctr=ae",
        "mobile": "https://www.propertyfinder.ae/agent/0/130/100/MODE/example/900001-profile.jpg?ctr=ae"
      }
    },
    "super_agent_award_image_url": "https://static.example.com/super-agent.jpg"
  },
  "metrics": {
    "ranking": 95,
    "listing_level": 0,
    "median_listing_quality": 96,
    "total_properties": 17,
    "property_counts": {
      "residential_for_rent": 0,
      "residential_for_sale": 17,
      "commercial_for_rent": 0,
      "commercial_for_sale": 0
    }
  },
  "service_area": {
    "top_locations": [
      {
        "id": "41",
        "name": "Downtown Dubai"
      },
      {
        "id": "36",
        "name": "Business Bay"
      }
    ]
  },
  "reviews": {
    "average_rating": 5,
    "review_count": 2,
    "rating_distribution": {
      "score1": 0,
      "score2": 0,
      "score3": 0,
      "score4": 0,
      "score5": 2
    }
  },
  "performance": {
    "avg_whatsapp_response_time": 31,
    "transactions": {
      "visible": true,
      "count": 7,
      "claimed_sale": 6,
      "claimed_rent": 1,
      "deal_volume": 58750000,
      "recent": [
        {
          "location": {
            "path": "1.41.604.12155",
            "community": "Downtown Dubai",
            "tower": "Burj Khalifa Zone 3"
          },
          "dealType": "Sale",
          "price": 5100000,
          "date": "2026-04-03",
          "propertyType": "Apartment",
          "bedroom": "2"
        }
      ]
    }
  },
  "attributes": {
    "languages": [
      {
        "id": "1",
        "name": "English"
      }
    ],
    "compliances": [
      {
        "type": "brn",
        "value": "900001"
      }
    ]
  },
  "fingerprint": "exampleagent00000001"
}

Example: agency (record_type = "agency")

{
  "record_type": "agency",
  "record_id": "5001",
  "source_context": {
    "source_name": "Property Finder UAE",
    "source_domain": "propertyfinder.ae",
    "page_index": 1,
    "search_position": 1,
    "seed_id": "a7ef02c27a18a41f0b97",
    "seed_type": "search",
    "category": "companies"
  },
  "entity": {
    "id": "5001",
    "url": "https://www.propertyfinder.ae/en/broker/example-prime-real-estate-5001",
    "slug": "example-prime-real-estate-5001",
    "name": "Example Prime Real Estate LLC",
    "description": "Example brokerage description for public directory records.",
    "external_ids": {
      "propertyfinder_agency_id": "5001",
      "propertyfinder_client_id": "5001"
    }
  },
  "brokerage": {
    "license": {
      "number": "25831",
      "label": "RERA"
    },
    "is_verified": false,
    "client": {
      "id": "5001",
      "type": "broker",
      "segment_weight": 4000,
      "tier_weight": 0
    },
    "branch": {
      "parent_id": "0",
      "is_main_branch": true,
      "total_branches": 0
    }
  },
  "location": {
    "address": "Office 1204, Example Business Tower, Business Bay, Dubai, United Arab Emirates",
    "city": "Dubai",
    "location_id": "1"
  },
  "contact_details": {
    "email": "info@example.com",
    "phone": "+971500000000"
  },
  "media": {
    "logo": {
      "url": "https://static.shared.propertyfinder.ae/media/images/client_logos/5001/example-logo/260x200.jpg",
      "links": {
        "desktop": "https://static.shared.propertyfinder.ae/media/images/client_logos/5001/example-logo/260x200.jpg",
        "mobile": "https://static.shared.propertyfinder.ae/media/images/client_logos/5001/example-logo/130x100.jpg"
      }
    }
  },
  "metrics": {
    "ranking": 99.7,
    "total_agents": 31,
    "total_super_agents": 10,
    "total_branches": 0,
    "total_properties": 672,
    "transactions_count": 4,
    "property_counts": {
      "residential_for_rent": 250,
      "residential_for_sale": 416,
      "commercial_for_rent": 4,
      "commercial_for_sale": 2
    }
  },
  "attributes": {
    "awards": [
      "https://static.example.com/award.jpg"
    ]
  },
  "fingerprint": "exampleagency0000001"
}

Field Reference

• record_type (string, required): agent for individual agent profiles or agency for brokerage/company records.
• record_id (string, required): Stable Property Finder identifier for the saved entity.
• source_context (object, required): Source identity and collection context, including source_name, source_domain, page index, search position, seed metadata, category, specialization, and search location when available.
• entity (object, required): Primary public identity, including id, url, slug, name, description, and external_ids.
• agent (object, agent records): Agent-specific profile details such as user id, role, biography, nationality, license number, LinkedIn URL, SuperAgent flag, verification flag, and experience year.
• brokerage (object): Broker identity for agent rows, or agency license, client, branch, and verification details for agency rows.
• location (object, agency records): Agency address, city, and public location id when available.
• contact_details (object): Public email, phone, and WhatsApp channels when exposed by the source.
• media (object): Agent profile images, agency logos, media paths, tokens, and image variant links.
• metrics (object): Ranking, listing quality, property counts, agent counts, branch counts, transaction counts, and other public numeric source metrics.
• service_area (object, agent records): Agent top locations and related market coverage data.
• reviews (object, agent records): Average rating, review count, and rating distribution.
• performance (object, agent records): WhatsApp response-time value and visible transaction-history metrics.
• attributes (object): Additional meaningful source details such as languages, compliances, awards, and source-specific values.
• fingerprint (string, required): Compact record fingerprint for comparison and deduplication.

Data Quality, Guarantees, And Handling

• Structured records: results are normalized into predictable JSON objects for downstream use.
• Best-effort extraction: fields may vary by region, session, availability, or UI experiments.
• Optional fields: null-check in downstream code because public records can differ in completeness.
• Deduplication: use record_id as the strongest stable key, with entity.url or fingerprint as secondary comparison keys when needed.
• Freshness: results reflect the publicly available data at run time.
• Repeated runs: use the recommended idempotency key when syncing data into warehouses, CRMs, or search indexes.

Tips For Best Results

• Start with a small limit to validate the output shape before scaling up.
• Use one category per run when you need clean separation between agents and companies.
• Add a location when you need a focused market segment, such as Dubai Marina or Business Bay.
• Leave location empty when the goal is broad UAE discovery.
• Use specialization only for agent runs; company runs ignore it.
• Add filters gradually to understand how each field changes coverage.
• Use stable identifiers for deduplication when storing results over time.

How to Run on Apify

1. Open the Actor in Apify Console.
2. Configure category, location, and specialization for the target scope.
3. Set limit to the maximum number of outputs to collect.
4. Click Start and wait for the run to finish.
5. Open the dataset and inspect the first records.
6. Download results in JSON, CSV, Excel, or other supported formats.

Scheduling & Automation

Scheduling

Automated Data Collection

Schedule runs to keep agent and company datasets fresh for recurring reporting, enrichment, or monitoring workflows. Use a cadence that matches your operational needs and the level of change you expect in the target market.

• Navigate to Schedules in Apify Console
• Create a new schedule, such as daily, weekly, or custom cron
• Configure input parameters
• Enable notifications for run completion
• Add webhooks for automated processing

Integration Options

• CRM enrichment: sync public agent, broker, contact, location, and rating attributes into lead or account records.
• Google Sheets or Airtable: review smaller agent and company datasets with sales, research, or operations teams.
• Webhooks: trigger validation, notification, or ingestion workflows after each completed run.
• Data enrichment pipelines: join Property Finder public profile attributes with existing CRM, BI, or research datasets.
• BI dashboards: monitor agent counts, company coverage, ratings, property counts, and transaction signals over time.
• API access: ingest JSON records directly into internal services, warehouse loaders, or search indexes.

Export Formats And Downstream Use

Apify datasets can be exported or consumed by downstream systems for operational analysis, reporting, and data delivery.

• JSON: for APIs, applications, and data pipelines
• CSV or Excel: for spreadsheet workflows and manual review
• API access: for automated ingestion into internal systems
• BI and warehouses: for reporting, dashboards, and historical analysis

Performance

Estimated run times:

• Small runs (< 1,000 outputs): ~3-5 minutes
• Medium runs (1,000-5,000 outputs): ~5-15 minutes
• Large runs (5,000+ outputs): ~15-30 minutes

Execution time varies based on filters, result volume, and how much information is returned per record. Highly filtered runs can finish faster, while broad discovery or detail-rich records may take longer.

Limitations

• Availability depends on what www.propertyfinder.ae/en/find-broker publicly exposes at run time.
• Some optional fields may be missing on sparse or limited public records.
• Very broad searches may take longer or require higher limits.
• Target-side changes can affect field availability, naming, or visible results.
• Regional, account, or availability differences may change what records are visible.
• Company searches do not use the specialization field.

Troubleshooting

• No results returned: check filter values, location spelling, category selection, and whether the target has matching public records.
• Fewer results than expected: broaden filters, raise limit, or verify that enough matching public records exist.
• Some fields are empty: optional fields depend on what each public record provides.
• Run takes longer than expected: reduce scope, lower limit for validation, or split broad collection into smaller segments.
• Output changed: compare the current output with the field reference and report a small sample if support is needed.

FAQ

What data does this actor collect?

It collects public Property Finder UAE agent and agency/company records. Agent records can include contact details, brokerage information, ratings, languages, top locations, property counts, profile metadata, and public transaction history when available.

Can I filter by location, category, date, price, or other criteria?

You can filter by category, location, and agent specialization. The input schema does not include date, price, sort, or radius filters.

Why did I receive fewer results than my limit?

The run may finish with fewer records when the selected category, location, and specialization contain fewer matching public results than the requested limit.

Can I schedule recurring runs?

Yes. Use Apify schedules to run the actor daily, weekly, or on a custom cadence for monitoring, reporting, or enrichment workflows.

How do I avoid duplicates across runs?

Use record_id as the primary idempotency key. For additional checks, compare entity.url or fingerprint when those fields are present.

Can I export the data to CSV, Excel, or JSON?

Yes. Apify datasets support JSON, CSV, Excel, and other export formats from the dataset view.

Does this actor collect private data?

No. It is intended to collect publicly available information visible on Property Finder UAE public directory records.

What should I include when reporting an issue?

Include the input used, the run ID, expected versus actual behavior, and a small output sample when available. Redact any information you do not want to share.

Compliance & Ethics

Responsible Data Collection

This actor collects publicly available real estate agent and company directory information from www.propertyfinder.ae/en/find-broker for legitimate business purposes, including:

• Real estate research and market analysis
• Lead enrichment and account research
• Competitive monitoring and operational reporting

This section is informational and not legal advice. Users are responsible for ensuring their use of collected data complies with applicable laws, regulations, and platform terms.

Best Practices

• Use collected data in accordance with applicable laws, regulations, and the target site's terms
• Respect individual privacy and personal information
• Use data responsibly and avoid disruptive or excessive collection
• Do not use this actor for spamming, harassment, or other harmful purposes
• Follow relevant data protection requirements where applicable, such as GDPR and CCPA

Support

For help, use the actor page or Issues section. Include the input used with sensitive values redacted, the run ID, expected versus actual behavior, and a small output sample if it helps illustrate the issue.