Ascension Works Tax Sale Listings Scraper

Step 2 of 3: collect, normalize, and filter authorized current listings for the counties selected in Step 1.

Paste the secure research handle from Step 1. The service resolves the exact customer scope, uses only currently approved collection routes, extracts allowlisted listing facts, and returns a sanitized listing set plus a secure listing handle for Step 3. No customer workbook or route address is required.

Independent research utility. Not affiliated with or endorsed by any government agency, county, auction platform, or data provider.

About Ascension Works

Ascension Works is a venture operated by Arete Praxis LLC. The original software, documentation, configuration, and product presentation for this Actor are proprietary intellectual property of Arete Praxis LLC under the Ascension Works brand. Public records, official government materials, and third-party materials remain subject to their respective rights and terms.

Try the other Ascension Works scrapers

• U.S. County Research Scraper checks customer-scoped research availability across up to 1,000 counties or county equivalents.
• Tax Sale Ranking Scraper compares counties and ranks authorized listings using your selected criteria.

Secure three-step mode

You can choose 1 to 1,000 counties or county equivalents across multiple states or territories, one or two years, freshness and page limits, budget/value filters, property and sale-method preferences, and a deterministic ordering profile. Step 1 returns a signed, expiring research handle bound to that exact customer and scope. This Actor rejects altered, expired, or cross-customer handles before collection.

Collection runs only for a route with current approvals for access, automation, commercial use, factual field scope, and customer delivery. The result excludes route addresses, credentials, page content, owner/contact fields, and implementation details before anything reaches customer storage. A strict customer-supplied fallback remains available when the customer affirms the right to use those records.

maxResults is the listing page size, not a claim that a fixed cap represents the complete result. The request summary reports the exact number evaluated, excluded, qualifying, returned, and remaining, plus complete, held, and failed jurisdiction counts. When another page exists, it returns both a signed, expiring continuation cursor and a secure listing handle. Paste both on the next run; the Actor reopens the exact encrypted snapshot instead of recollecting pages that may have changed. A run is never labeled complete while any requested jurisdiction remains held, failed, or only partially collected.

Known starting amounts are not predicted final acquisition prices. The Actor does not establish title, lien priority, redemption rights, eligibility, condition, value, or investment merit.

Controlled output

Customers select jurisdictions and pass the Step 1 handle. The service maps the confirmed scope to eligible routes, collects only allowlisted factual fields, and removes route addresses and implementation details before any customer result is stored. Unsupported, expired, changed, or unapproved routes return a truthful unavailable/manual-review outcome and no paid listing result.

Data handling

Your input and final output are stored in this Actor run's Apify default storages and follow your Apify account's access and retention settings. Customer-supplied mode is processed inside this run.

When an eligible service-side route is used, the bounded request is sent to a restricted Ascension Works-owned Apify run. After its result is copied and validated, this Actor deletes that temporary run's default input, output, and queue storages. If it cannot confirm all three deletions, no research result is delivered. Minimal service logs record only product type, output count, and status; Apify may retain generic run metadata and logs under its platform policies.

Do not submit owner or taxpayer names, mailing or contact details, credentials, raw pages, or other unnecessary personal data. If you enable Apify developer run sharing or attach a run to an Actor Issue, Apify may provide the creator access to the shared run's input, output, and logs.

Support and corrections

Use the Actor's Apify Issue or support control for a reproducible normalization problem. Include only the run ID, affected factual field, and generic status; never post credentials, private records, or personal data. Schema, freshness, and permission rules are periodically rechecked, and affected processing may be held unavailable while a correction is reviewed.

Early-release status

This early release supports the secure Step 1-to-Step 2 workflow plus a strict customer-supplied fallback. Collection is limited to separately authorized routes; jurisdiction recognition is not a promise that current listings are available everywhere. The approved all-in price for each eligible current_listing_normalized result that is actually stored is $0.000770 FREE, $0.0007315 BRONZE, $0.000693 SILVER, or $0.0006545 GOLD, plus the $0.00005 Actor-start event. Platform usage is included. Set at least $0.00082 as the run charge authorization when one paid result is requested. Summary, excluded, stale, duplicate, unauthorized, unavailable, and held rows do not receive the custom paid-result event.