Pricing

Rating

Developer

Actor stats

Categories

Share

Auction.com Scraper

Slug: fatihtahta/auction-com-scraper

Overview

Auction.com Scraper collects structured property auction listings from Auction.com, including listing identifiers, property addresses, pricing signals, auction timing, venue details, property characteristics, media, documents, and source-specific auction terms when available. Auction.com is a public real estate auction marketplace where investors, analysts, operators, and research teams can monitor auction inventory and public listing activity. The actor helps teams turn Auction.com search pages, category pages, and listing pages into repeatable JSON datasets for discovery, monitoring, reporting, enrichment, and competitive intelligence workflows. Users can run small validation jobs, larger recurring collections, or detail-enriched listing checks using the same input contract. Results are delivered as structured Apify dataset records suitable for review, export, and downstream processing. The actor is designed for dependable recurring data acquisition while remaining transparent about source-side variability and optional field availability.

Who Should Use This Actor

• Market research and analytics teams: monitor auction inventory, property attributes, estimated values, opening bids, geography, and auction timing for market intelligence.
• Real estate investment teams: build repeatable property research workflows around trustee sales, foreclosure listings, public auction events, and comparable listing attributes.
• Product, marketplace, and catalog teams: normalize public property auction records into internal databases, listing review queues, or content operations systems.
• Developers and data engineering teams: feed structured extraction results into ETL jobs, warehouses, search indexes, analytics tools, and downstream systems.
• AI agents and workflow automations: collect scoped property auction datasets, compare repeated runs, summarize changes, and route records to review or enrichment steps.
• Monitoring and operations teams: track listing status, auction dates, venue information, and detail availability across scheduled collection workflows.
• Sales, lead generation, and enrichment teams: use public property, party, contact, and location fields where available to enrich approved internal workflows.

Common Use Cases

• Auction inventory monitoring: track public Auction.com listings across selected search pages, regions, categories, or known listing URLs.
• Property research: collect addresses, property types, bedrooms, bathrooms, square footage, lot area, year built, occupancy status, and source reports when present.
• Pricing and valuation analysis: compare starting bids, seller current values, estimated values, currency, and auction terms across repeated runs.
• Auction event tracking: monitor auction dates, venue details, event codes, trustee sale indicators, and status labels for operational reporting.
• Detail enrichment: revisit known listing URLs with richer collection enabled to capture additional media, documents, contacts, parties, and listing remarks.
• Recurring reporting: schedule repeatable runs for dashboards, alerts, trend analysis, and historical comparisons.
• Segmented analysis: keep separate runs by search URL, category page, geography, or listing group to support cleaner downstream comparison.
• Agentic research workflows: let an internal agent collect a bounded dataset, validate records against the field reference, and pass records to summarization or review workflows.

Real-World Questions This Data Can Answer

• Which public Auction.com listings match a specific search page, category page, geography, or known set of listing URLs?
• Which properties have new or changed auction timing, listing status, venue details, or pricing signals compared with a previous run?
• Which listings have enough property, media, document, contact, or party detail to support deeper review?
• Which addresses, counties, states, or property types are represented in a selected auction inventory segment?
• Which records should be updated, inserted, or deduplicated in an internal warehouse based on stable listing identifiers?
• Which auction terms, trustee sale indicators, occupancy details, or source-specific attributes require human review?
• Which optional fields are sufficiently populated for dashboards, alerts, or downstream enrichment workflows?

Quick Start

1. Choose one or more Auction.com search result pages, category pages, or individual listing pages for startUrls.
2. Set a small limit, such as 10 or 25, for the first validation run.
3. Decide whether enrich_data is needed for richer listing details or whether standard listing fields are enough.
4. Run the actor in Apify Console.
5. Inspect the first dataset records to confirm identifiers, property fields, pricing fields, auction timing, and optional enrichment fields match your use case.
6. Increase the limit, add more URLs, export results, or schedule the actor once the output is verified.

Input Parameters

Provide one or more Auction.com URLs, optionally enable richer listing details, and set a per-query save limit.

Choosing Inputs

Use startUrls when you already know the Auction.com search result pages, category pages, or listing pages you want to collect. Search and category URLs are best for discovery because they can return multiple matching listings from the selected public page scope. Individual listing URLs are best for targeted checks, enrichment, and repeatable monitoring of known properties.

Use limit to control coverage and cost of review. A small limit is useful for validating the output shape, while a larger limit is appropriate after you confirm that the chosen URLs produce the listings you need.

Use enrich_data when downstream workflows need richer listing records, such as full media arrays, documents, party details, auction terms, contact details, property reports, and listing remarks where available. Leave it off when standard listing records are sufficient or when speed is more important than detail depth.

When running multiple market segments, keep separate input configurations for each geography, category page, or business workflow. Segmented runs make it easier to compare counts, deduplicate records, and diagnose changes later.

Input Recipes

• Validation run: use one Auction.com search or category URL in startUrls, keep limit low, and leave enrich_data off until you confirm the standard record shape.
• Targeted listing review: provide one or more individual listing URLs in startUrls, set a small limit, and enable enrich_data when you need detailed property, media, document, contact, or party fields.
• Broad discovery: provide a broader search or category page in startUrls, choose a practical limit, and review the first records before scaling to a larger run.
• Monitoring run: repeat the same startUrls, limit, and enrich_data setting on a schedule so changes can be compared across runs.
• Segmented analysis: run separate inputs for each search page, category page, geography, or internal workflow name so downstream reports can compare segments cleanly.
• Enrichment pass: start from known listing URLs matched to an internal system, enable enrich_data, and upsert the returned records by record_id.

Example Inputs

Example: Search page validation run

{
"startUrls":[
"https://www.auction.com/residential/26.361645418238187,-129.1526449272487,47.2563363379616,-102.5217855522487_bounds/active_lt/auction_date_order,resi_sort_v2_st/y_nbs"
],
"limit":10,
"enrich_data":false
}

Example: Detail-enriched known listings

{
"startUrls":[
"https://www.auction.com/details/3434-w-thoreau-ln-anthem-az-2007705",
"https://www.auction.com/details/8316-w-jayne-crest-st-magna-ut-2029773"
],
"limit":25,
"enrich_data":true
}

Example: Recurring segment collection

{
"startUrls":[
"https://www.auction.com/residential/26.361645418238187,-129.1526449272487,47.2563363379616,-102.5217855522487_bounds/active_lt/auction_date_order,resi_sort_v2_st/y_nbs"
],
"limit":100,
"enrich_data":true
}

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, AI agents, and downstream APIs with minimal post-processing.

The provided output contract contains one primary record shape: a property listing record identified by record_type = "property_listing".

Record envelope and stable identifiers

Each dataset item is a listing record with a stable envelope and nested property, listing, pricing, location, media, contact, relationship, and attribute groups when available.

Recommended idempotency key: record_id. This value corresponds to the Auction.com listing identifier and is also repeated as listing.listing_id, entity.external_ids.listing_id, and source_context.external_ids.listing_id when available.

Use source_context.canonical_url or source_context.listing_url as a secondary audit key when reconciling records. For deduplication and upserts, match on record_id first and preserve URL fields for traceability. Stable identifiers make records easier to merge, deduplicate, sync, and compare across repeated runs.

source_context stores provenance fields including source name, domain, source URL, listing URL, canonical URL, seed type, seed value, external IDs, enrichment status, detail URL, and enrichment source when present.

Examples

Example: listing record

{
"record_type":"property_listing",
"record_id":"2007705",
"source_context":{
"source_name":"Auction.com",
"source_domain":"auction.com",
"source_url":"https://www.auction.com/residential/26.361645418238187,-129.1526449272487,47.2563363379616,-102.5217855522487_bounds/active_lt/auction_date_order,resi_sort_v2_st/y_nbs",
"listing_url":"https://www.auction.com/details/3434-w-thoreau-ln-anthem-az-2007705",
"canonical_url":"https://www.auction.com/details/3434-w-thoreau-ln-anthem-az-2007705",
"seed_type":"url",
"seed_value":"https://www.auction.com/residential/26.361645418238187,-129.1526449272487,47.2563363379616,-102.5217855522487_bounds/active_lt/auction_date_order,resi_sort_v2_st/y_nbs",
"external_ids":{
"listing_id":"2007705",
"urn":"adc:listing:2007705",
"property_id":"1376813",
"trinity":"701Rg00000fcgcBIAQ"
},
"enriched":true,
"detail_url":"https://www.auction.com/details/3434-w-thoreau-ln-anthem-az-2007705",
"enrichment_source":"listing_detail_page"
},
"entity":{
"title":"3434 W Thoreau Ln, Anthem, AZ 85086, Maricopa County",
"url":"https://www.auction.com/details/3434-w-thoreau-ln-anthem-az-2007705",
"status":"SALE_PENDING_CLEARED",
"external_ids":{
"listing_id":"2007705",
"urn":"adc:listing:2007705",
"property_id":"1376813"
}
},
"listing":{
"listing_id":"2007705",
"listing_type":"TRUSTEE",
"deal_type":"auction",
"listing_status":"SALE_PENDING_CLEARED",
"listing_status_group":"ACTIVE",
"listing_status_label":"Cleared",
"is_new_listing":false,
"auction":{
"start_date":"2026-06-18T17:00:00Z",
"visible_auction_start_date_time":"2026-06-18T17:00:00Z",
"is_online":false,
"venue_type":"LIVE",
"event_code":"E-31361",
"trustee_sale":true,
"auction_date":"2026-06-18",
"event_title":"Arizona Public Foreclosure Sale (E-31361)",
"event_type":"LIVE",
"event_id":"3524937",
"event_description":"E-31361 Arizona",
"venue_id":"3524941",
"venue_code":"FY",
"venue_title":"Maricopa County Properties",
"venue_name":"Maricopa County Courthouse - Main Entrance to the Superior Court Building",
"bid_start_local_date":"2026-06-18",
"bid_start_local_time":"10:00:00"
}
},
"pricing":{
"starting_bid":537600,
"seller_current_value":660000,
"estimated_value":595176,
"currency":"USD",
"earnest_money_deposit_commission_type":"DOLLAR",
"buyers_premium_commission_type":"DOLLAR"
},
"location":{
"address":"3434 W THOREAU LN",
"full_address":"3434 W Thoreau Ln, Anthem, AZ 85086, Maricopa County",
"street":"3434 W THOREAU LN",
"city":"ANTHEM",
"county":"Maricopa",
"state":"AZ",
"postal_code":"85086",
"country":"United States",
"country_code":"US",
"latitude":33.8458166,
"longitude":-112.1341771,
"coordinates":{
"latitude":33.8458166,
"longitude":-112.1341771
}
},
"property":{
"property_id":"1376813",
"property_type":"SINGLE_FAMILY",
"property_subtype":"SINGLE_FAMILY_HOME",
"bedrooms":5,
"bathrooms":4,
"floor_area":3366,
"floor_area_sqft":3366,
"lot_area":0.15,
"year_built":2000,
"property_taxonomy":{
"structure_type_code":"SINGLE_FAMILY_HOME",
"structure_type_group":"SINGLE_FAMILY"
},
"apn":"203-10-588",
"first_activation_date":"2026-03-10T16:30:09Z",
"vendor_report_url":"https://adc-tenbox-prod.imgix.net/datalake/pir_reports/AECF0FACA0E84192AD7B445BC63D243C.v1.pdf",
"property_report_url":"https://adc-tenbox-prod.imgix.net/datalake/pir_reports/AECF0FACA0E84192AD7B445BC63D243C.v1.pdf",
"has_vendor_information_available":true,
"parcel_numbers":[
"203-10-588"
],
"address_parts":{
"street_number":"3434",
"street_name":"W Thoreau Ln"
}
},
"availability":{
"occupancy_status":"OCCUPIED",
"interior_access_allowed":false,
"title_insurance":"NOT_OFFERED"
},
"media":{
"main_image_url":"https://adc-tenbox-prod.imgix.net/resi/propertyImages/1376813/4617893ord00812471_1-edited.v1.jpeg?auto=compress,format",
"image_urls":[
"https://adc-tenbox-prod.imgix.net/resi/propertyImages/1376813/4617893ord00812471_1-edited.v1.jpeg?auto=compress,format",
"https://adc-tenbox-prod.imgix.net/resi/propertyImages/1376813/4617894ord00812471_2-edited.v1.jpeg?auto=compress,format",
"https://adc-tenbox-prod.imgix.net/resi/propertyImages/1376813/4617895ord00812471_3-edited.v1.jpeg?auto=compress,format",
"https://adc-tenbox-prod.imgix.net/resi/propertyImages/1376813/4616487ord00812471_4.v1.jpeg?auto=compress,format",
"https://adc-tenbox-prod.imgix.net/resi/propertyImages/1376813/4616492ord00812471_5.v1.jpeg?auto=compress,format"
],
"media_count":5,
"listing_photos_count":5,
"documents":[
{
"url":"https://adc-tenbox-prod.imgix.net/resi/globalDocuments/B34DF8496FB742EAB4073ADB4B69EED9.v16.pdf",
"title":"Foreclosure Sale Terms and Conditions",
"file_name":"Trustee Sale Terms and Conditions (AZ).pdf",
"purpose":"TERMS_AND_CONDITIONS",
"content_type":"application/pdf",
"description":"Trustee Sale Terms and Conditions (AZ)"
},
{
"url":"https://auction.box.com/shared/static/j6pveg8ihimoboo4ln4itz3n9ibplryh.pdf",
"title":"Sample Trustee Deed Upon Sale",
"file_name":"AZ_Deed.pdf",
"purpose":"SAMPLE_DEED",
"content_type":"application/pdf",
"description":"Sample Trustee Deed Upon Sale (AZ)"
},
{
"url":"https://auction.box.com/shared/static/x8zevjos7oz6ngbw9266ekd9so2jtx2v.pdf",
"title":"IRS Form 8300",
"file_name":"IRS Form 8300.pdf",
"purpose":"TAX_FORM",
"content_type":"application/pdf",
"description":"IRS Form 8300"
},
{
"url":"https://auction.box.com/shared/static/0gt4kshqgcfvagpuofhk6t9ob8vbzaw2.pdf",
"title":"Sample Certificate of Sale/Receipt",
"file_name":"AZ_CertofSale.pdf",
"purpose":"SAMPLE_TRUSTEE_CERT_OF_SALE",
"content_type":"application/pdf",
"description":"Sample Certificate of Sale/Receipt (AZ)"
}
],
"document_urls":[
"https://adc-tenbox-prod.imgix.net/resi/globalDocuments/B34DF8496FB742EAB4073ADB4B69EED9.v16.pdf",
"https://auction.box.com/shared/static/j6pveg8ihimoboo4ln4itz3n9ibplryh.pdf",
"https://auction.box.com/shared/static/x8zevjos7oz6ngbw9266ekd9so2jtx2v.pdf",
"https://auction.box.com/shared/static/0gt4kshqgcfvagpuofhk6t9ob8vbzaw2.pdf"
]
},
"attributes":{
"tags":[
"RURL"
],
"auction_terms":{
"product_type":"TRUSTEE",
"asset_type":"FORECLOSURE",
"is_reserve_displayed":true,
"buyer_premium_available":false,
"is_direct_offer_enabled":false,
"is_reserve_price_available":true,
"is_proxy_bidding_enabled":true,
"is_earnest_money_deposit_available":false,
"is_first_look_enabled":false,
"program_configuration":{
"buyers_premium_commission_type":"DOLLAR",
"earnest_money_deposit_commission_type":"DOLLAR",
"program_enrollment_code":"FMT"
},
"listing_summary":{
"is_remote_bid_enabled":true,
"show_opening_bid":true,
"is_remote_before_and_during_auction_enabled":true
}
},
"source_specific":{
"attribution_source":"AUCTION_COM",
"venue_type":"LIVE",
"event_code":"E-31361",
"trustee_sale":true,
"external_identifiers":[
{
"external_identifier":"701Rg00000fcgcBIAQ",
"data_source":"TRINITY"
}
],
"seller_property":{
"street_description":"3434 W THOREAU LN",
"country_primary_subdivision":"AZ",
"country_secondary_subdivision":"Maricopa",
"municipality":"ANTHEM",
"postal_code":"85086"
}
},
"enrichment":{
"enriched":true,
"detail_url":"https://www.auction.com/details/3434-w-thoreau-ln-anthem-az-2007705"
},
"marketing_attributes":{
"auctioneer_dialogue_clearance":{
"label":"Dialog",
"message":" Trustee Sale Number 145426-AZ with a property address of 3434 W THOREAU LN, ANTHEM, AZ, APN , . On behalf of the creditor I have been authorized to open the bidding at $537600.00.",
"show":true
},
"nos_amount":{
"show":false
},
"general_announcement":{
"message":"Announcer or Auctioneer: This is a general announcement. If you have a question regarding a specific property, please visit the Information Booth. If you are the junior creditor, a protected junior creditor, or if you have a bankruptcy notice or other court notice, please visit the [WHERE TO GO] before the calling of the sales. Remote bids will be accepted at today’s auction for certain properties. \n\nAll remote bidders are required to deposit funds in advance of the auction in an amount sufficient to pay for their remote bids. Please visit auction.com/remotebid if you are interested in participating as a remote bidder INTRO The Auctioneer has the authority to conduct foreclosure sales and postponements on behalf of the Trustee. Auctioneer has no authority to accept tender, reinstatement, or payoff funds from any party without final approval/confirmation from the foreclosure attorney. Properties sold at a Trustee Sale are sold on an \"as is, where is\" basis without representations or warranties, of any nature, express or implied, bidders must conduct their investigation concerning conditions of title, market value, legal standing , physical condition and history of property. Caveat emptor or \"Let the buyer beware\" applies to these auctions. Any representations or warranties made by the Auctioneer concerning any particular property are not made pursuant to the express written instructions of the Trustee and are deemed to be outside the scope of the Trustees Auctioneers employment and may not be imputed to the Trustee. Auctioneer at this Trustee sale may have more than one sale or postponement to cry, the crying of all other sales and postponements will be deemed to be commenced at the time the Trustees auctioneer cries the first sale or postponement of a group of one or more sales or postponements scheduled to be conducted at the same time. Bidders believed to be colluding to limit competitive bidding may be reported to the appropriate authorities and/or may be disqualified from bidding. Once qualification of the bidders is closed and the bidding has begun, Trustee reserves the right to refuse to reopen the qualification process to accommodate any late applications for qualification to bid. \n\nAll bids are irrevocable. To qualify as a bidder at a trustees sale, the prospective bidder, unless already qualified by the Trustee, must be in attendance and must provide the Auctioneer with the following: 1. Bidders name, address, telephone number; 2. The maximum amount the bidder may contemplate bidding at the sale, this amount must exceed the initial minimum bid; and, 3. A deposit in the amount of $10,000 prior to the commencement of the sale as provided in Arizona Revised Statutes Section 33-810. This deposit shall be returned to all bidders except the bidder whose bid resulted in the highest price. The highest bidder at the sale shall pay the remainder of the bid price in a form satisfactory to the Trustee no later than 5:00 pm Mountain Standard Time on the business day following this sale. In addition to cash, the Trustee will accept cashier's checks drawn on a state or national bank, a state or federal credit union, by a state or federal savings and loan association, savings association, or savings bank as defined by state law and authorized to do business in this state. Cashier's checks must be made payable to the order of Bidder's Name or Trustee. Foreign cashier’s checks will not be accepted. All persons tendering funds and payee(s) for cashier’s checks must be present and provide valid government‑issued identification prior to acceptance of payment. Cashier's checks without a specified valid thru date will be accepted up to 180 days after the issue date. Auctioneer or Trustee require a prospective bidder to provide a valid US Government-issued form of identification upon being declared the Winning Bidder. All Third Parties tendering funds in the form of cash must comply with the IRS reporting requirements, Publication 1544. For more information see www.irs.gov. \n\nDuring the bidding process, Auctioneer may, at the instruction of the Trustee, enter subsequent bids on behalf of the creditor up to the amount of the total obligation that is due. All bids must be net bids to the Trustee. The purchaser must pay all costs of the transfer including title insurance, if any, all taxes and recording fees. During the period between the sale and the Trustee’s issuance of the Trustees deed, bids accepted by the Trustee cannot be withdrawn or cancelled. Pursuant to ARS 33-811 (as amended by HB2033), the trustee must record the trustee's deed. The winning bidder is responsible for paying the cost of recording the trustee's deed to the trustee along with the balance of the winning bid. Please contact the applicable trustee if you have questions regarding this process. The announcing of the postponements will begin momentarily. Please note that all postponements are listed on the website at www.auction.com and also noted on the board. \n\nPlease be advised that certain purchasers may be required to disclose identifying and beneficial ownership of trusts or entities listed as the purchaser to the Trustee or foreclosure law firm. For more information, please reach out to the Trustee/Law Firm associated with the property. \n\n\n ",
"show":false
},
"auctioneer_dialogue_postponement":{
"label":"Dialog",
"message":" Trustee Sale Number 145426-AZ , 3434 W THOREAU LN, ANTHEM, AZ, , has been postponed until at due to .",
"show":true
},
"opening_bid":{
"show":true,
"default_display_value":"HIDDEN"
},
"trustee_sale_number":{
"label":"Trustee Sale Number",
"show":true
},
"deposit_check_verbiage":{
"message":"<p>A Winning Bid Deposit of $10,000 is required for each property purchased. Pay in-person or with Remote Bid. The balance is due by 5 pm the next business day. Interested in remote bidding? <a href=\"https://www.auction.com/lp/az-remote-bid-deposit/\" rel=\"nofollow\">Learn more</a></p>\n<p><br></p>\n<p>To pay the Winning Bid Deposit:</p>\n<ul>\n <li>In-person Bidder: A cashier's check made payable to the bidder as a natural person (Not as a Legal Entity). All persons tendering funds and payee(s) for cashier’s checks must be present and provide valid government‑issued identification prior to acceptance of payment.</li>\n <li>Remote Bidder: Funds must be available in your Remote Bid account.</li>\n</ul>",
"show":false
},
"contact":{
"label":"Contact (for Borrowers/Homeowners)",
"message":"404-994-7400",
"show":true
},
"cos_disclaimer":{
"message":"The sale may be rescinded due to requirements set out in both state and federal laws or regulations, including anti-money laundering, anti-terrorism, anti-drug trafficking and economic sanctions laws and regulations. Federal law requires all financial institutions to obtain, verify, and record information that identifies parties to transactions. This means that when your bid is provisionally accepted, you may be asked for your name, address, date of birth, and other information that will allow us to identify you. We may also ask to see your driver's license or other identifying documents to comply with such rules and regulations. Your bid is subject to verification of your identity and confirmation of compliance with all applicable laws and regulations. If you intend to take title in an entity or trust, you must provide all information required by FinCEN's Residential Real Estate Rule to the entity preparing the deed. If you do not provide this information timely, the sale may be rescinded, the deed may be withheld, or the deed may be vested in Bidder's name as an individual. \n\nBy signing below, Buyer's or Buyer's Representative's signature agree and confirm that (i) all of the above information is true and correct, (ii) the sale was conducted in accordance with all the terms, conditions, and disclaimers applicable to the sale, and (iii) a copy of this disclosure and the sale terms and conditions was received and reviewed. ",
"show":true
},
"disclaimer":{
"message":"DISCLAIMER: The content provided herein, including property photos and characteristics, has been gathered from various third parties and has not been verified. No representation or warranty is made by Auction.com regarding the accuracy or completeness of any content regarding the property. Property photos are not intended as a substitution for a bidder's own due diligence. Photos may not depict the condition of the property as it exists on the date of sale or closing. All bidders are responsible for conducting their own due diligence before bidding and are encouraged to seek independent professional advice if necessary.",
"show":true
}
},
"listing_remarks":{
"legal_description":"LOT 701, OF ANTHEM UNIT 12, ACCORDING TO THE PLAT OF RECORD IN THE OFFICE OF THE COUNTY RECORDER OF MARICOPA COUNTY, ARIZONA RECORDED IN BOOK 538 OF MAPS, PAGE 12"
},
"metrics":{
"listing_pdp_view_count":204,
"property_pdp_view_count":225
}
},
"contact_details":{
"emails":[
"crcinfo@clearreconcorp.com1",
"realestatereportsubmission@aldridgepite.com"
],
"phone_numbers":[
"858-750-7777",
"(202) 752-6046"
],
"parties":[
{
"role":"SERVICER",
"name":"Mr. Cooper"
},
{
"role":"BENEFICIARY",
"name":"LAKEVIEW LOAN SERVICING, LLC"
},
{
"role":"TRUSTOR",
"name":"FOREST JUSTIN TURNER AND LINNAE TURNER, HUSBAND AND WIFE AS COMMUNITY PROPERTY WITH RIGHT OF SURVIVORSHIP"
},
{
"role":"FORECLOSURE_ATTORNEY_CONTACT",
"name":"Clear Recon Corp",
"phone":"858-750-7777"
},
{
"role":"ORIGINAL_BENEFICIARY",
"name":"MORTGAGE ELECTRONIC REGISTRATION SYSTEMS, INC., AS BENEFICIARY, AS NOMINEE FOR MORIA DEVELOPEMENT INC., DBA PEOPLES MORTGAGE, ITS SUCCESSORS AND ASSIGNS"
},
{
"role":"INVESTOR",
"name":"Fannie Mae",
"phone":"(202) 752-6046"
},
{
"role":"FORECLOSURE_ATTORNEY",
"name":"Clear Recon Corp",
"email":"crcinfo@clearreconcorp.com1",
"phone":"858-750-7777"
},
{
"role":"FORECLOSURE_ATTORNEY_FINCEN_CONTACT",
"name":"Clear Recon Corp",
"email":"realestatereportsubmission@aldridgepite.com"
}
]
},
"relationships":{
"seller_code":"FMT",
"seller_plan_code":"FMT",
"seller_parties":[
{
"role":"SERVICER",
"name":"Fannie Mae"
},
{
"role":"PARENT_SELLER",
"name":"Fannie Mae"
},
{
"role":"INVESTOR",
"name":"Fannie Mae"
},
{
"role":"FORECLOSURE_ATTORNEY",
"name":"Fannie Mae"
}
],
"parties":[
{
"role":"SERVICER",
"name":"Mr. Cooper"
},
{
"role":"BENEFICIARY",
"name":"LAKEVIEW LOAN SERVICING, LLC"
},
{
"role":"TRUSTOR",
"name":"FOREST JUSTIN TURNER AND LINNAE TURNER, HUSBAND AND WIFE AS COMMUNITY PROPERTY WITH RIGHT OF SURVIVORSHIP"
},
{
"role":"FORECLOSURE_ATTORNEY_CONTACT",
"name":"Clear Recon Corp",
"phone":"858-750-7777"
},
{
"role":"ORIGINAL_BENEFICIARY",
"name":"MORTGAGE ELECTRONIC REGISTRATION SYSTEMS, INC., AS BENEFICIARY, AS NOMINEE FOR MORIA DEVELOPEMENT INC., DBA PEOPLES MORTGAGE, ITS SUCCESSORS AND ASSIGNS"
},
{
"role":"INVESTOR",
"name":"Fannie Mae",
"phone":"(202) 752-6046"
},
{
"role":"FORECLOSURE_ATTORNEY",
"name":"Clear Recon Corp",
"email":"crcinfo@clearreconcorp.com1",
"phone":"858-750-7777"
},
{
"role":"FORECLOSURE_ATTORNEY_FINCEN_CONTACT",
"name":"Clear Recon Corp",
"email":"realestatereportsubmission@aldridgepite.com"
}
]
}
}

Field Reference

Record Envelope

• record_type (string, required): record discriminator; the provided shape uses property_listing.
• record_id (string, required): stable Auction.com listing identifier for matching, deduplication, and upserts.

Source Context

• source_context.source_name (string, required): source marketplace name.
• source_context.source_domain (string, required): source website domain.
• source_context.source_url (string, required): input search, category, or listing URL that produced the record.
• source_context.listing_url (string, required): public listing URL for review and auditing.
• source_context.canonical_url (string, required): canonical public listing URL when available.
• source_context.seed_type (string, required): input type that produced the record.
• source_context.seed_value (string, required): original input value that led to the record.
• source_context.external_ids (object, optional): source listing, property, URN, and related identifiers.
• source_context.external_ids.listing_id (string, optional): Auction.com listing ID.
• source_context.external_ids.urn (string, optional): source URN for the listing.
• source_context.external_ids.property_id (string, optional): source property identifier.
• source_context.external_ids.trinity (string, optional): additional source identifier when available.
• source_context.enriched (boolean, optional): whether the record includes richer listing detail fields.
• source_context.detail_url (string, optional): detail page URL used for enriched listing context.
• source_context.enrichment_source (string, optional): label describing the enrichment source.

Entity

• entity.title (string, required): human-readable listing title, usually based on address and county.
• entity.url (string, required): public listing URL.
• entity.status (string, optional): current source listing status.
• entity.external_ids (object, optional): listing, URN, and property identifiers associated with the entity.
• entity.external_ids.listing_id (string, optional): Auction.com listing ID.
• entity.external_ids.urn (string, optional): source URN.
• entity.external_ids.property_id (string, optional): source property ID.

Listing

• listing.listing_id (string, required): Auction.com listing identifier.
• listing.listing_type (string, optional): listing type or auction product category.
• listing.deal_type (string, optional): transaction context, such as auction.
• listing.listing_status (string, optional): detailed source listing status.
• listing.listing_status_group (string, optional): high-level source status group.
• listing.listing_status_label (string, optional): displayed status label.
• listing.is_new_listing (boolean, optional): whether the source marks the listing as new.
• listing.auction.start_date (string, optional): auction start timestamp when available.
• listing.auction.visible_auction_start_date_time (string, optional): displayed auction start timestamp.
• listing.auction.is_online (boolean, optional): whether the auction is marked as online.
• listing.auction.venue_type (string, optional): auction venue type.
• listing.auction.event_code (string, optional): source event code.
• listing.auction.trustee_sale (boolean, optional): whether the auction is marked as a trustee sale.
• listing.auction.auction_date (string, optional): auction date.
• listing.auction.event_title (string, optional): event title.
• listing.auction.event_type (string, optional): event type.
• listing.auction.event_id (string, optional): source event ID.
• listing.auction.event_description (string, optional): event description.
• listing.auction.venue_id (string, optional): source venue ID.
• listing.auction.venue_code (string, optional): source venue code.
• listing.auction.venue_title (string, optional): source venue title.
• listing.auction.venue_name (string, optional): venue name.
• listing.auction.bid_start_local_date (string, optional): local bid start date.
• listing.auction.bid_start_local_time (string, optional): local bid start time.

Pricing

• pricing.starting_bid (number, optional): starting bid amount in the listed currency.
• pricing.seller_current_value (number, optional): seller current value in the listed currency.
• pricing.estimated_value (number, optional): estimated value in the listed currency.
• pricing.currency (string, optional): currency code; the provided example uses USD.
• pricing.earnest_money_deposit_commission_type (string, optional): source commission type for earnest money deposit.
• pricing.buyers_premium_commission_type (string, optional): source commission type for buyer premium.

Location

• location.address (string, optional): source address line.
• location.full_address (string, optional): formatted full address.
• location.street (string, optional): street address.
• location.city (string, optional): city or municipality.
• location.county (string, optional): county.
• location.state (string, optional): state abbreviation.
• location.postal_code (string, optional): postal code.
• location.country (string, optional): country name.
• location.country_code (string, optional): country code.
• location.latitude (number, optional): latitude coordinate.
• location.longitude (number, optional): longitude coordinate.
• location.coordinates.latitude (number, optional): latitude in the nested coordinates object.
• location.coordinates.longitude (number, optional): longitude in the nested coordinates object.

Property

• property.property_id (string, optional): source property identifier.
• property.property_type (string, optional): source property type.
• property.property_subtype (string, optional): source property subtype.
• property.bedrooms (number, optional): bedroom count.
• property.bathrooms (number, optional): bathroom count.
• property.floor_area (number, optional): floor area value when available.
• property.floor_area_sqft (number, optional): floor area in square feet.
• property.lot_area (number, optional): lot area value as provided by the source.
• property.year_built (number, optional): year built.
• property.property_taxonomy.structure_type_code (string, optional): source structure type code.
• property.property_taxonomy.structure_type_group (string, optional): source structure type group.
• property.apn (string, optional): assessor parcel number when available.
• property.first_activation_date (string, optional): first activation timestamp.
• property.vendor_report_url (string, optional): vendor report URL when available.
• property.property_report_url (string, optional): property report URL when available.
• property.has_vendor_information_available (boolean, optional): whether vendor information is marked available.
• property.parcel_numbers (array of strings, optional): parcel numbers associated with the property.
• property.address_parts.street_number (string, optional): parsed street number.
• property.address_parts.street_name (string, optional): parsed street name.

Availability

• availability.occupancy_status (string, optional): occupancy status when provided.
• availability.interior_access_allowed (boolean, optional): whether interior access is marked as allowed.
• availability.title_insurance (string, optional): title insurance value when provided.

Media

• media.main_image_url (string, optional): primary image URL.
• media.image_urls (array of strings, optional): image URLs associated with the listing.
• media.media_count (number, optional): count of media items when provided.
• media.listing_photos_count (number, optional): count of listing photos when provided.
• media.documents (array of objects, optional): document objects associated with the listing.
• media.documents.url (string, optional): document URL.
• media.documents.title (string, optional): document title.
• media.documents.file_name (string, optional): document file name.
• media.documents.purpose (string, optional): document purpose label.
• media.documents.content_type (string, optional): document MIME type.
• media.documents.description (string, optional): document description.
• media.document_urls (array of strings, optional): document URLs extracted from document objects.

Attributes

• attributes.tags (array of strings, optional): source tags associated with the listing.
• attributes.auction_terms.product_type (string, optional): auction product type.
• attributes.auction_terms.asset_type (string, optional): asset type.
• attributes.auction_terms.is_reserve_displayed (boolean, optional): whether reserve information is displayed.
• attributes.auction_terms.buyer_premium_available (boolean, optional): whether buyer premium is marked available.
• attributes.auction_terms.is_direct_offer_enabled (boolean, optional): whether direct offer is marked enabled.
• attributes.auction_terms.is_reserve_price_available (boolean, optional): whether reserve price is marked available.
• attributes.auction_terms.is_proxy_bidding_enabled (boolean, optional): whether proxy bidding is marked enabled.
• attributes.auction_terms.is_earnest_money_deposit_available (boolean, optional): whether earnest money deposit is marked available.
• attributes.auction_terms.is_first_look_enabled (boolean, optional): whether first-look access is marked enabled.
• attributes.auction_terms.program_configuration.buyers_premium_commission_type (string, optional): buyer premium commission type.
• attributes.auction_terms.program_configuration.earnest_money_deposit_commission_type (string, optional): earnest money deposit commission type.
• attributes.auction_terms.program_configuration.program_enrollment_code (string, optional): program enrollment code.
• attributes.auction_terms.listing_summary.is_remote_bid_enabled (boolean, optional): whether remote bidding is marked enabled.
• attributes.auction_terms.listing_summary.show_opening_bid (boolean, optional): whether opening bid is marked for display.
• attributes.auction_terms.listing_summary.is_remote_before_and_during_auction_enabled (boolean, optional): whether remote bidding before and during auction is marked enabled.
• attributes.source_specific.attribution_source (string, optional): source attribution label.
• attributes.source_specific.venue_type (string, optional): venue type.
• attributes.source_specific.event_code (string, optional): event code.
• attributes.source_specific.trustee_sale (boolean, optional): trustee sale marker.
• attributes.source_specific.external_identifiers (array of objects, optional): additional source identifiers.
• attributes.source_specific.external_identifiers.external_identifier (string, optional): external identifier value.
• attributes.source_specific.external_identifiers.data_source (string, optional): external identifier source.
• attributes.source_specific.seller_property.street_description (string, optional): seller-side street description.
• attributes.source_specific.seller_property.country_primary_subdivision (string, optional): seller-side primary subdivision.
• attributes.source_specific.seller_property.country_secondary_subdivision (string, optional): seller-side secondary subdivision.
• attributes.source_specific.seller_property.municipality (string, optional): seller-side municipality.
• attributes.source_specific.seller_property.postal_code (string, optional): seller-side postal code.
• attributes.enrichment.enriched (boolean, optional): whether enrichment details are present.
• attributes.enrichment.detail_url (string, optional): detail URL associated with enrichment.
• attributes.marketing_attributes (object, optional): source-provided listing messages and display flags.
• attributes.marketing_attributes.auctioneer_dialogue_clearance.label (string, optional): clearance dialogue label.
• attributes.marketing_attributes.auctioneer_dialogue_clearance.message (string, optional): clearance dialogue message.
• attributes.marketing_attributes.auctioneer_dialogue_clearance.show (boolean, optional): display flag for clearance dialogue.
• attributes.marketing_attributes.nos_amount.show (boolean, optional): display flag for NOS amount.
• attributes.marketing_attributes.general_announcement.message (string, optional): general announcement text.
• attributes.marketing_attributes.general_announcement.show (boolean, optional): display flag for general announcement.
• attributes.marketing_attributes.auctioneer_dialogue_postponement.label (string, optional): postponement dialogue label.
• attributes.marketing_attributes.auctioneer_dialogue_postponement.message (string, optional): postponement dialogue message.
• attributes.marketing_attributes.auctioneer_dialogue_postponement.show (boolean, optional): display flag for postponement dialogue.
• attributes.marketing_attributes.opening_bid.show (boolean, optional): display flag for opening bid.
• attributes.marketing_attributes.opening_bid.default_display_value (string, optional): default display value for opening bid.
• attributes.marketing_attributes.trustee_sale_number.label (string, optional): trustee sale number label.
• attributes.marketing_attributes.trustee_sale_number.show (boolean, optional): display flag for trustee sale number.
• attributes.marketing_attributes.deposit_check_verbiage.message (string, optional): deposit instructions text.
• attributes.marketing_attributes.deposit_check_verbiage.show (boolean, optional): display flag for deposit instructions.
• attributes.marketing_attributes.contact.label (string, optional): contact label.
• attributes.marketing_attributes.contact.message (string, optional): contact value.
• attributes.marketing_attributes.contact.show (boolean, optional): display flag for contact.
• attributes.marketing_attributes.cos_disclaimer.message (string, optional): compliance or sale disclosure text.
• attributes.marketing_attributes.cos_disclaimer.show (boolean, optional): display flag for compliance or sale disclosure.
• attributes.marketing_attributes.disclaimer.message (string, optional): listing disclaimer text.
• attributes.marketing_attributes.disclaimer.show (boolean, optional): display flag for listing disclaimer.
• attributes.listing_remarks.legal_description (string, optional): legal property description when provided.
• attributes.metrics.listing_pdp_view_count (number, optional): listing page view count at run time.
• attributes.metrics.property_pdp_view_count (number, optional): property page view count at run time.

Contact Details

• contact_details.emails (array of strings, optional): email addresses found in the public listing detail.
• contact_details.phone_numbers (array of strings, optional): phone numbers found in the public listing detail.
• contact_details.parties (array of objects, optional): party records associated with the listing.
• contact_details.parties.role (string, optional): party role.
• contact_details.parties.name (string, optional): party name.
• contact_details.parties.email (string, optional): party email when present.
• contact_details.parties.phone (string, optional): party phone when present.

Relationships

• relationships.seller_code (string, optional): seller code.
• relationships.seller_plan_code (string, optional): seller plan code.
• relationships.seller_parties (array of objects, optional): seller-side party records.
• relationships.seller_parties.role (string, optional): seller party role.
• relationships.seller_parties.name (string, optional): seller party name.
• relationships.parties (array of objects, optional): party records associated with the property or listing.
• relationships.parties.role (string, optional): party role.
• relationships.parties.name (string, optional): party name.
• relationships.parties.email (string, optional): party email when present.
• relationships.parties.phone (string, optional): party phone when present.

Data Model Notes

• Identity fields: use record_id as the primary matching key for deduplication, upserts, and repeated-run comparisons.
• Source and provenance fields: use source_context.source_url, source_context.listing_url, source_context.canonical_url, source_context.seed_type, and source_context.seed_value to trace records back to their public source and input scope.
• Business attributes: listing, pricing, location, property, availability, media, attributes, contact_details, and relationships carry the main operational value for review and downstream analysis.
• Metrics and counts: fields such as media.media_count, media.listing_photos_count, attributes.metrics.listing_pdp_view_count, and attributes.metrics.property_pdp_view_count should be treated as point-in-time values.
• Nested objects: related values are grouped together so JSON-first systems can preserve context without flattening away meaning.
• Optional fields: many fields depend on listing type, region, public availability, detail depth, and source-side data quality; downstream code should treat them as nullable.
• Repeated runs: compare records by record_id plus Apify run metadata, run date, and input configuration stored alongside the dataset export.

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, availability, account visibility, UI experiments, or source-side changes.
• Optional fields: null-check in downstream code and dashboards.
• Deduplication: use record_id as the strongest stable key, with source_context.canonical_url or source_context.listing_url as secondary audit keys.
• Freshness: results reflect the publicly available data at run time.
• Repeated runs: use the recommended idempotency key when syncing data into warehouses, CRMs, search indexes, vector stores, or monitoring systems.
• Schema awareness: downstream systems should rely on documented fields and handle newly missing optional fields gracefully.

Tips For Best Results

• Start with a small limit to validate the output shape before scaling up.
• Use one search page, category page, geography, or listing segment per run when you need cleaner comparison.
• Use individual listing URLs when you need targeted collection for known properties.
• Enable enrich_data only when richer detail fields are needed for the workflow.
• Schedule recurring runs for monitoring workflows instead of relying on manual one-off jobs.
• Use record_id for deduplication when storing results over time.
• Keep a saved copy of the input configuration used for each recurring workflow.
• Review a small sample after changing startUrls, increasing limit, or enabling enrich_data.

How to Run on Apify

1. Open the Actor in Apify Console.
2. Configure startUrls for the target search pages, category pages, or listing pages.
3. Set limit to control the maximum number of saved listings per query.
4. Choose whether to enable enrich_data.
5. Click Start and wait for the run to finish.
6. Open the dataset, inspect the first records, and download results in JSON, CSV, Excel, or another supported format.

Agentic And API-First Usage

Auction.com Scraper can be used as a structured data acquisition step inside larger automated workflows. It gives agents, schedulers, and downstream services a stable input surface and a documented JSON output contract for property auction records.

Agent workflow pattern:

1. Generate or select a scoped input from the supported schema.
2. Run the actor manually, on a schedule, or through Apify platform automation.
3. Wait for completion and read the dataset records.
4. Validate records against the field reference.
5. Upsert records into the downstream system using record_id.
6. Trigger analysis, enrichment, alerts, or human review.

Practical notes for agentic use:

• Keep prompts and automations grounded in startUrls, limit, and enrich_data.
• Start with small validation runs before allowing broad automated collection.
• Feed the Field Reference and a small output sample to downstream AI steps.
• Treat optional fields as nullable instead of asking agents to infer missing values.
• Store run ID, input configuration, and dataset export metadata outside the record when building audit trails.

Scheduling & Automation

Scheduling

Automated Data Collection

Schedule runs to keep Auction.com listing datasets fresh for monitoring, reporting, and change detection. Use the same input configuration across runs when you need comparable results over time.

• 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 auction inventory, pricing signals, listing status, geography, and property attributes over time.
• Data warehouses: store normalized property auction records for historical analysis and reporting.
• Webhooks: trigger validation, notification, or ingestion workflows after each completed run.
• CRM and enrichment pipelines: sync public listing, property, party, contact, and location attributes into approved internal records.
• Google Sheets or Airtable: review smaller validation runs, shortlists, and operational queues.
• Search or vector indexes: support property discovery, semantic search, retrieval workflows, and agent context.
• Zapier or Make: connect completed runs to no-code alerts, review workflows, and lightweight operational handoffs.

Export Formats And Downstream Use

• JSON: for APIs, applications, AI agents, and data pipelines that need nested record fidelity.
• CSV or Excel: for spreadsheet workflows, stakeholder review, and lightweight analysis.
• API access: for automated ingestion into internal systems.
• BI and warehouses: for reporting, dashboards, historical analysis, and monitoring.
• Search or vector indexes: for discovery, semantic search, retrieval workflows, or agent context.

Downstream Pipeline Guide

• Idempotency: use record_id for upserts and preserve source_context.canonical_url as a traceability field.
• Null handling: treat optional fields as nullable, especially detail-only fields under media, contact_details, relationships, attributes, and property.
• Type handling: preserve numbers, booleans, arrays, and nested objects when exporting to JSON-first systems.
• Flattening: if exporting to CSV or Excel, flatten nested objects deliberately and keep the original JSON export for full fidelity.
• Partitioning: store run date, input segment, geography, category, workflow name, and Apify run ID outside or alongside records for easier analysis.
• Change detection: compare repeated runs by record_id and selected business fields such as listing.listing_status, listing.auction.auction_date, pricing.starting_bid, and availability.occupancy_status.
• Quality checks: monitor record count, duplicate rate, required identifiers, URL presence, and important optional field fill rates.
• Human review: route records with missing critical fields, unusual pricing values, changed status, or new contact and party details into a review queue when needed.
• Retention: decide how long to keep raw exports versus normalized warehouse tables based on your use case.

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, target availability, and how much information is returned per record. Highly targeted runs can finish faster, while broad discovery or detail-rich records may take longer.

Limitations

• Availability depends on what https://www.auction.com publicly exposes at run time.
• Some optional fields may be missing on sparse records or listing types that do not publish those details.
• Very broad search or category URLs may take longer or require a higher limit.
• Source-side changes can affect field availability, naming, or population rates.
• Regional, account, visibility, or availability differences may change visible results.
• The actor provides structured public data, not business advice, legal advice, valuation advice, or guaranteed completeness.

Troubleshooting

• No results returned: check the provided URLs and confirm that Auction.com has matching public records for the selected page or listing.
• Fewer results than expected: raise limit, verify that the source page contains enough matching listings, or split collection into clearer segments.
• Some fields are empty: optional fields depend on what each record publicly provides and whether detail enrichment is enabled.
• Duplicate-looking records: compare record_id first, then review URL and status fields to decide whether records represent updates or variants.
• Run takes longer than expected: reduce scope, lower limit for validation, or split broad collection into smaller URL groups.
• Output changed: compare the current output with the Field Reference and report a small sample if support is needed.
• Downstream import failed: check JSON validity, nullable fields, nested objects, and whether your destination expects flattened columns.

FAQ

What data does this actor collect?

It collects public Auction.com property auction listing records, including listing identity, source URLs, property attributes, pricing fields, auction timing, location, media, availability, and enriched details where available.

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

The input schema accepts Auction.com URLs through startUrls. Use Auction.com search result pages or category pages that already represent the location, category, date, price, status, keyword, or other scope you want to collect.

Why did I receive fewer results than my limit?

The limit is a maximum, not a guarantee. A run may save fewer records when the provided URLs expose fewer matching public listings or when the available public records are sparse.

How should I choose a limit for my first run?

Start with a small limit, such as 10 or 25, inspect the dataset shape, then increase the limit after confirming that the selected URLs produce useful records.

Can I schedule recurring runs?

Yes. Use Apify schedules to run the same input configuration repeatedly for monitoring, reporting, and change detection workflows.

How do I avoid duplicates across runs?

Use record_id as the primary unique key. Keep source_context.canonical_url and source_context.listing_url for audit and reconciliation.

What is the best field to use as a unique key?

record_id is the recommended idempotency key for property listing records.

Can I use the output with AI agents or automated workflows?

Yes. The actor writes structured JSON dataset records that can be read by AI agents, ETL pipelines, warehouses, search indexes, and workflow automations.

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

Yes. Apify datasets can be exported in JSON, CSV, Excel, and other supported formats. Keep JSON when you need full nested field fidelity.

Does this actor collect private data?

The actor is intended for publicly available Auction.com listing information. Users are responsible for using the dataset in accordance with applicable laws, regulations, and the target site's terms.

What should I include when reporting an issue?

Include the input used, with sensitive context redacted if needed, the run ID, expected versus actual behavior, a small output sample if available, and the downstream destination or export format if the issue is pipeline-related.

Compliance & Ethics

Responsible Data Collection

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

• Real estate research and market analysis
• Auction inventory monitoring and operational reporting
• Property research and investment workflow support

Users are responsible for ensuring that their collection, retention, sharing, and use of the data comply with applicable laws, regulations, contractual obligations, and platform 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, discrimination, or other harmful purposes.
• Follow relevant data protection requirements where applicable, for example GDPR, CCPA, or sector-specific rules.
• Review your own retention, access control, and data-sharing policies before operationalizing the dataset.

Support

For help, use Issues or the actor page on Apify. Include the input used, redacted if needed, the run ID, expected versus actual behavior, an optional small output sample, and the downstream destination or export format if the issue is pipeline-related.