Leilão Imóvel Scraper

Slug: fatihtahta/leilao-imovel-scraper

Overview

Leilão Imóvel collects structured Brazilian real estate auction listing data, including property details, pricing, discounts, dates, location, sale terms, payment eligibility, documents, images, and listing metadata. Leilão Imóvel is a public marketplace for real estate auction opportunities, making its data useful for market research, opportunity screening, acquisition workflows, and recurring portfolio analysis. The actor converts public listing information into repeatable JSON records that are easier to review, export, compare, and load into downstream systems. It is designed for automated, recurring data acquisition with consistent output fields and practical filtering options. Results reflect the public data available at run time, enabling dependable operational workflows without assuming completeness beyond what the source exposes.

Why Use This Actor

• Market research and analytics teams: build structured extraction workflows for pricing, discounts, asset classes, locations, banks, and sale formats across Brazilian real estate auction listings.
• Product and content teams: populate internal property feeds, research tools, content operations, and review queues with normalized listing data.
• Developers and data engineering teams: feed downstream systems, warehouses, enrichment pipelines, and monitoring workflows with predictable JSON records.
• Lead generation and enrichment teams: identify target properties, locations, seller contexts, payment conditions, and broker information for qualification workflows.
• Monitoring and competitive tracking teams: schedule recurring collection to track availability, pricing movement, auction deadlines, and geographic supply changes.

Common Use Cases

• Market intelligence: monitor auction supply, pricing, discount levels, property types, bank exposure, and geographic distribution.
• Acquisition screening: filter listings by state, city, price range, discount, property type, payment eligibility, sale type, or sale modality.
• Lead generation: build targeted prospect or opportunity lists from public real estate auction listings and related broker information.
• Competitive monitoring: track changes in available listings, auction timing, sale formats, and institution coverage over repeated runs.
• Catalog and directory building: populate internal databases with structured public property records, images, documents, and location fields.
• Data enrichment: add current public auction attributes to CRM, BI, portfolio, or analytics datasets.
• Recurring reporting: schedule periodic runs for dashboards, alerts, intake reviews, and market movement analysis.

Quick Start

1. Choose the target scope using location, price, property type, discount, payment option, sale type, sale modality, date, bank, or limit fields.
2. For the first validation run, set a small limit such as 25 or 50.
3. Run the actor in Apify Console.
4. Inspect the first dataset records and confirm the fields match your reporting, review, or ingestion workflow.
5. Broaden or narrow filters after validation, then increase limit for production collection.
6. Schedule the actor when you need recurring monitoring or refreshed datasets.

Input Parameters

This actor accepts optional filters for location, price, property type, discount, financing, sale format, dates, banks, and maximum result count.

Parameter	Type	Description	Default
location_state	string	Brazilian state name or abbreviation, such as SP, RJ, or Minas Gerais. Use it to focus results on one state.	–
location_city	string	Brazilian city name. For precise regional filtering, combine it with location_state.	–
min_price	integer	Minimum property price to include, in Brazilian reais (BRL). Must be at least 1 when provided.	–
max_price	integer	Maximum property price to include, in Brazilian reais (BRL). Must be at least 1 when provided.	–
property_type	array of strings	Property types to include. Allowed values: Agency, Apartment, Industrial Land, Rural Land, House, Commercial Property, Warehouse, Parking Space, Unspecified, Other, Land / Plot.	–
min_discount	string	Minimum discount percentage to include. Allowed values: 0, 5, 10, 15, 20, 25, 30, 35, 40, 45, 50, 55, 60, 65, 70, 75, 80, 85, 90, 95, 100.	–
max_discount	string	Maximum discount percentage to include. Allowed values: 0, 5, 10, 15, 20, 25, 30, 35, 40, 45, 50, 55, 60, 65, 70, 75, 80, 85, 90, 95, 100.	–
financement_method	array of strings	Payment methods listings must support. Allowed values: FGTS (Severance Fund), Financing.	–
sale_type	array of strings	Sale types to include. Allowed values: Direct Purchase, Online Sale, Open Bidding (Caixa), SFI Auction (Caixa).	–
condo_debt	array of strings	Condo debt conditions to include. Allowed values: Buyer Pays Condo Debt, Buyer Pays up to 10% of Appraised Value.	–
sale_modality	array of strings	Sale modalities to include. Allowed values: PGFN Acquisition, Extrajudicial Auction, Judicial Auction, Other, Private Sale, Direct Sale.	–
auction_end_before	string	Latest auction end date to include. Use an Apify date picker value to include listings ending on or before the selected date.	–
listing_date_from	string	Earliest listing inclusion date to include. Use an Apify date picker value to focus on listings added on or after the selected date.	–
banks	array of strings	Banks to include. Allowed values: Caixa Econômica Federal CEF, Banco do Brasil, Banco BRB, Banco Inter, Banco Santander, Bradesco, Emgea, Fundação Assefaz, Itaú Unibanco.	–
limit	integer	Maximum number of listings to save for this run configuration. Must be at least 1 when provided. Leave empty to collect as many matching records as available during the run.	–

Choosing Inputs

Use narrower filters when you need a targeted dataset, such as one state, one city, a defined price band, a specific property type, or listings with a minimum discount. Use broader filters when the goal is discovery, market mapping, or a more complete view of available public listings. Location fields control geographic scope, price and discount fields control financial screening, property type controls asset category, and date fields help align records with your review window. Bank, sale type, sale modality, payment option, and condo debt fields are useful when your operating process only accepts certain transaction structures. Start with a small limit to validate output quality, then increase it after confirming the records match your downstream workflow.

Example Inputs

Location and Property Type Review

{
  "location_state": "SP",
  "location_city": "São Paulo",
  "property_type": ["Apartment", "House"],
  "min_price": 150000,
  "max_price": 800000,
  "limit": 50
}

Discount-Focused Opportunity Screening

{
  "location_state": "SC",
  "property_type": ["House", "Land / Plot"],
  "min_discount": "40",
  "sale_type": ["Online Sale", "Direct Purchase"],
  "banks": ["Caixa Econômica Federal CEF"],
  "limit": 75
}

Recent Listing Monitoring

{
  "location_state": "RJ",
  "listing_date_from": "2026-04-01",
  "auction_end_before": "2026-06-30",
  "financement_method": ["Financing"],
  "sale_modality": ["Judicial Auction", "Extrajudicial Auction"],
  "limit": 100
}

Output

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.

When multiple entity types or record shapes exist, this README documents each shape separately based on the provided Example Output.

Record Envelope And Stable Identifiers

The documented output shape is a real estate auction listing record. The strongest recommended idempotency key is id; use url or fingerprint as a secondary key when reconciling records across systems.

For deduplication and upserts, store records by id and update mutable listing fields such as prices, dates, availability-related text, and payment terms on later runs. Stable identifiers make records easier to merge, deduplicate, and sync across repeated runs. The fingerprint field provides an additional stable record signature, and sourceUrl records the public search or listing context associated with the collected record.

Examples

Example: listing

{
  "id": "2295647",
  "url": "https://www.leilaoimovel.com.br/imovel/sc/xanxere/residencial-lot-bem-morar-3-quartos-2-vagas-na-garagem-varanda-sacada-area-de-servico-imovel-caixa-economica-federal-cef-2295647-1444417607230-venda-direta-caixa",
  "title": "Casa Caixa em Xanxerê / SC - 2295647",
  "address": "RUA RENATO MARCANTE,N. 106 LT 45, QD D, SAO JORGE - CEP: 89820-000, XANXERE - SANTA CATARINA",
  "imageUrl": "https://image.leilaoimovel.com.br/images/47/casa-caixa-em-xanxere-sc-2295647-imovel-2295647-03e5bad2e6b618b3f61f8376bc0d62a260ebe65b-g.webp",
  "currentPrice": "R$ 322.799,34",
  "appraisalPrice": "R$ 595.881,72",
  "discountPercent": 46,
  "closingDate": "28/04/2026 às 18:00",
  "categories": [
    "Venda Online"
  ],
  "propertyType": "Casa",
  "city": "Xanxerê",
  "state": "SC",
  "detailPageUrl": "https://www.leilaoimovel.com.br/imovel/sc/xanxere/residencial-lot-bem-morar-3-quartos-2-vagas-na-garagem-varanda-sacada-area-de-servico-imovel-caixa-economica-federal-cef-2295647-1444417607230-venda-direta-caixa",
  "usableArea": "329,79 m²",
  "landArea": "371,00 m²",
  "bedrooms": 3,
  "parkingSpaces": 2,
  "detailAlerts": [
    "Encerra em: 28/04/2026 às 18:00",
    "Imóvel NÃO ACEITA Financiamento",
    "Imóvel NÃO ACEITA Parcelamento",
    "Imóvel NÃO ACEITA FGTS",
    "Somente à vista",
    "Condomínio: Sob responsabilidade do comprador, até o limite de 10% em relação ao valor de avaliação do imóvel. A CAIXA realizará o pagamento apenas do valor que exceder o limite de 10% do valor de avaliação.",
    "Tributos: Sob responsabilidade do comprador.",
    "Existe área não averbada. Corretores credenciados"
  ],
  "acceptsFinancing": false,
  "acceptsInstallments": false,
  "acceptsFgts": false,
  "cashOnly": true,
  "paymentTerms": "Somente à vista",
  "caixaAccreditedBroker": "LEILÃO IMÓVEL IMOBILIÁRIA",
  "creciState": "SC",
  "creciNumber": "8491",
  "locationText": "SC /Xanxerê",
  "propertyTypeDetail": "Casa /Venda Online",
  "bank": "Caixa",
  "originCode": "1444417607230",
  "propertyCode": "2295647",
  "inclusionDate": "02/06/2025",
  "registrationNumber": "33273",
  "judicialDistrict": "XANXERE-SC",
  "registryOffice": "01",
  "realEstateRegistration": "19779",
  "negativeAuctionsAnnotation": "Averbado",
  "description": "LOT BEM MORAR - 3 Quartos, 2 Vagas na Garagem, Varanda/sacada, Área de Serviço, 4 Wc, Sala, Cozinha. . RUA RENATO MARCANTE,N. 106 LT 45, QD D, SAO JORGE - CEP: 89820-000, XANXERE - SANTA CATARINA - Condomínio: Sob responsabilidade do comprador, até o limite de 10% em relação ao valor de avaliação do imóvel. A CAIXA realizará o pagamento apenas do valor que exceder o limite de 10% do valor de avaliação. - Tributos: Sob responsabilidade do comprador. - Existe área não averbada. Corretores credenciados",
  "documents": [
    {
      "label": "Matricula",
      "url": "https://venda-imoveis.caixa.gov.br/editais/matricula/SC/1444417607230.pdf"
    },
    {
      "label": "Edital",
      "url": "https://venda-imoveis.caixa.gov.br/editais/regras-VOL/comocomprar.pdf?v=01"
    }
  ],
  "imageUrls": [
    "https://image.leilaoimovel.com.br/images/47/casa-caixa-em-xanxere-sc-2295647-imovel-2295647-03e5bad2e6b618b3f61f8376bc0d62a260ebe65b-g.webp"
  ],
  "coordinates": {
    "latitude": -26.8612337,
    "longitude": -52.3947944
  },
  "detailLoadedUrl": "https://www.leilaoimovel.com.br/imovel/sc/xanxere/residencial-lot-bem-morar-3-quartos-2-vagas-na-garagem-varanda-sacada-area-de-servico-imovel-caixa-economica-federal-cef-2295647-1444417607230-venda-direta-caixa",
  "seed_id": "5fc3b6fbe36e",
  "seed_type": "url",
  "seed_value": "https://www.leilaoimovel.com.br/encontre-seu-imovel?s=&venda=1,11,10,7",
  "page_index": 1,
  "fingerprint": "a63f46422be81ed444ea",
  "sourceUrl": "https://www.leilaoimovel.com.br/encontre-seu-imovel?s=&venda=1%2C11%2C10%2C7"
}

Field Reference

Listing Record

id (string, required): Stable listing identifier.

url (string, required): Public listing URL.

title (string, required): Listing title.

address (string, optional): Public address text for the property.

imageUrl (string, optional): Primary image URL.

currentPrice (string, optional): Current listing price as displayed, in BRL.

appraisalPrice (string, optional): Appraisal value as displayed, in BRL.

discountPercent (number, optional): Discount percentage when available.

closingDate (string, optional): Auction or listing closing date as displayed by the source.

categories (array of strings, optional): Listing categories or sale labels.

propertyType (string, optional): Property type, such as house, apartment, land, warehouse, or commercial property.

city / state (string, optional): Municipality and Brazilian state abbreviation.

detailPageUrl (string, optional): Public detail page URL for the listing.

usableArea / landArea (string, optional): Property area values as displayed, typically in square meters (m²).

bedrooms / parkingSpaces (number, optional): Bedroom and parking space counts when provided.

detailAlerts (array of strings, optional): Public notices, conditions, payment restrictions, debt notes, or listing alerts.

acceptsFinancing / acceptsInstallments / acceptsFgts / cashOnly (boolean, optional): Payment eligibility and cash-only indicators.

paymentTerms (string, optional): Payment terms text.

caixaAccreditedBroker (string, optional): Accredited broker name when available.

creciState / creciNumber (string, optional): Broker CRECI registration state and number when available.

locationText (string, optional): Source-provided location label.

propertyTypeDetail (string, optional): Combined property type and sale label as displayed.

bank (string, optional): Bank or institution associated with the listing.

originCode (string, optional): Source-provided origin code.

propertyCode (string, optional): Source-provided property code.

inclusionDate (string, optional): Listing inclusion date as displayed.

registrationNumber (string, optional): Registration number when available.

judicialDistrict (string, optional): Judicial district associated with the property when provided.

registryOffice (string, optional): Registry office identifier when provided.

realEstateRegistration (string, optional): Real estate registration number when provided.

negativeAuctionsAnnotation (string, optional): Public annotation related to negative auctions when available.

description (string, optional): Public listing description and relevant conditions.

documents (array of objects, optional): Public document links associated with the listing.

documents.label (string, optional): Document label.

documents.url (string, optional): Public document URL.

imageUrls (array of strings, optional): All collected image URLs for the listing.

coordinates (object, optional): Geographic coordinates when available.

coordinates.latitude (number, optional): Latitude.

coordinates.longitude (number, optional): Longitude.

detailLoadedUrl (string, optional): Final public detail URL associated with the record.

seed_id (string, optional): Run context identifier for the input scope that produced the record.

seed_type (string, optional): Run context type for the input scope.

seed_value (string, optional): Input scope value associated with the record.

page_index (number, optional): Result page index associated with the record.

fingerprint (string, optional): Stable record fingerprint suitable as a secondary deduplication key.

sourceUrl (string, optional): Public source URL associated with the record collection context.

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 source-side presentation changes.
• Optional fields: null-check optional fields in downstream code, especially documents, coordinates, broker details, registration data, and payment indicators.
• Deduplication: use id as the primary stable key, with url or fingerprint as a secondary key 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 state, city, property type, bank, or sale segment per run when you need cleaner segmentation.
• Leave optional filters empty when the goal is broad discovery.
• Add filters gradually to understand how each field changes coverage.
• Use listing_date_from and auction_end_before for monitoring windows and recurring review cycles.
• Schedule recurring runs for monitoring workflows instead of relying on manual one-off collection.
• Store id, url, and fingerprint to support deduplication over time.

How To Run On Apify

1. Open the Actor in Apify Console.
2. Configure the available input fields for the target scope.
3. Set the maximum number of outputs to collect with limit, if you want a capped run.
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 property auction datasets fresh for monitoring, reporting, and enrichment workflows. Recurring runs are especially useful for tracking listing availability, auction deadlines, and changing market conditions.

• 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

• BI dashboards: monitor pricing, discounts, availability, property types, banks, and geographic coverage over time.
• Data warehouses: load normalized listing records into historical tables for analysis and reporting.
• CRM enrichment: sync property, broker, location, and sale-condition attributes into lead or opportunity records.
• Google Sheets or Airtable: review smaller regional or filtered runs in lightweight operational workflows.
• Webhooks: trigger validation, ingestion, notification, or alerting workflows after each completed run.
• Data enrichment pipelines: combine auction listing records with internal portfolio, risk, valuation, or acquisition datasets.

Export Formats And Downstream Use

Apify datasets can be exported or consumed by downstream systems for operational review, analysis, and automation.

• 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–10 minutes
• Medium runs (1,000–5,000 outputs): ~8–25 minutes
• Large runs (5,000+ outputs): ~20–35 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 https://www.leilaoimovel.com.br publicly exposes at run time.
• Some optional fields may be missing on sparse listings or listing types with limited public detail.
• Very broad searches may take longer or require higher limit values.
• Source-side changes can affect field availability, labels, or naming.
• Regional, account, or availability differences may change visible results.
• Dates, prices, and sale conditions should be treated as time-sensitive public information and rechecked for critical decisions.

Troubleshooting

• No results returned: check filters, state or city spelling, selected categories, date windows, and whether the target has matching public records.
• Fewer results than expected: broaden filters, raise limit, or verify that enough matching public listings are available.
• Some fields are empty: optional fields depend on what each listing publicly provides.
• Run takes longer than expected: reduce scope, lower limit for validation, or split broad collection into smaller regional or category segments.
• Output changed: compare the current output with the field reference and include a small sample if support is needed.

FAQ

What data does this actor collect?

It collects public real estate auction listing data from Leilão Imóvel, including property details, prices, discounts, dates, location, sale terms, documents, images, payment indicators, and listing metadata.

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

Yes. The actor supports filters for state, city, price range, property type, discount range, payment options, sale type, condo debt rules, sale modality, auction end date, listing inclusion date, banks, and result limit.

Why did I receive fewer results than my limit?

limit is a maximum, not a guaranteed count. The actor may return fewer records when the public source has fewer matching listings for the selected filters.

Can I schedule recurring runs?

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

How do I avoid duplicates across runs?

Use id as the primary idempotency key when storing records. You can also retain url and fingerprint as secondary keys for reconciliation.

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

Yes. Apify datasets support exports in JSON, CSV, Excel, and other formats available in Apify Console.

Does this actor collect private data?

No. The actor is intended to collect publicly available listing information from Leilão Imóvel.

Are prices and auction dates always current?

Results reflect the public data available at run time. For time-sensitive acquisition decisions, run the actor again or verify the listing directly on the source site.

What should I include when reporting an issue?

Include the input used, the run ID, expected versus actual behavior, and a small output sample if it helps illustrate the issue.

Compliance & Ethics

Responsible Data Collection

This actor collects publicly available real estate auction listing information from https://www.leilaoimovel.com.br for legitimate business purposes, including:

• Real estate research and market analysis
• Auction opportunity screening
• Portfolio monitoring and data enrichment

Users are responsible for ensuring that their use of collected data complies with applicable laws, regulations, and the target site’s terms. This section is informational and not legal advice.

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. Include the input used with any sensitive values redacted, the run ID, expected versus actual behavior, and a small output sample when it is useful for diagnosis.