County Property Records API — Owner, Tax, Assessor, Appraisal
Pricing
from $43.00 / 1,000 property records
County Property Records API — Owner, Tax, Assessor, Appraisal
Search public county assessor records by address, parcel number, or owner name. Return normalized ownership, tax, appraisal, and property data.
Pricing
from $43.00 / 1,000 property records
Rating
0.0
(0)
Developer
Muhammad Afzal
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
14 days ago
Last modified
Categories
Share
Free-plan limit: Apify free-plan runs can return at most 5 dataset records per run from this Actor, even if you request more.
Search public county assessor parcel data by property address, parcel number, or owner name and receive one consistent JSON schema for real-estate research, lead qualification, appraisal review, and tax workflows.
This Actor queries the public ArcGIS REST services published for the selected jurisdiction. It includes built-in field mappings for Denton County, Texas and Los Angeles County, California, plus an automatic adapter for other public ArcGIS FeatureServer and MapServer parcel layers.
What it extracts
| Group | Fields |
|---|---|
| Parcel identity | recordId, parcelNumber, alternateParcelNumber, county, state |
| Ownership | ownerName, ownerMailingAddress when the public source exposes them |
| Property | propertyAddress, legalDescription, propertyUse, yearBuilt, squareFeet, land area, bedrooms, bathrooms, units |
| Assessment | assessed land, improvement, and total values; appraised value; taxable value; roll year |
| Tax | taxAmount, taxArea, and exemption when available from the source |
| Provenance | sourceName, sourceUrl, and retrievedAt |
Unavailable public fields are returned as null, never guessed. Los Angeles County's built-in assessor roll does not publish owner names, owner mailing addresses, or tax-bill amounts through this source. Denton County's public parcel layer includes owner names and mailing fields but may not represent the newest certified roll; verify time-sensitive facts with the county office.
When to use it
Use this Actor for public-record research, appraisal comparisons, tax-area analysis, property lead enrichment, and normalized exports across supported county GIS layers. It is especially useful when downstream code or an AI agent needs stable field names instead of county-specific abbreviations.
Do not use it as a title report, legal boundary survey, ownership certification, tax-payment confirmation, or nationwide completeness guarantee. County publication policies vary. Some counties redact owner names, publish delayed rolls, omit tax bills, or do not expose a compatible public ArcGIS layer.
Input
| Field | Required | Description |
|---|---|---|
source | Yes | dentonCountyTx, losAngelesCountyCa, or customArcgis |
searchMode | Yes | address, parcelNumber, or ownerName |
query | Yes | Address text, parcel identifier, or owner name; 2–160 characters |
customLayerUrl | For custom | Public HTTPS ArcGIS layer URL ending in /FeatureServer/{id} or /MapServer/{id} |
maxResults | Yes | Result and billing cap from 1 to 500; default 25 |
Address search
{"source": "dentonCountyTx","searchMode": "address","query": "5 WOODHAVEN CT","maxResults": 10}
Parcel-number search
{"source": "losAngelesCountyCa","searchMode": "parcelNumber","query": "2004013020","maxResults": 1}
Custom public ArcGIS layer
{"source": "customArcgis","searchMode": "address","query": "MAIN ST","customLayerUrl": "https://example.gov/arcgis/rest/services/Parcels/FeatureServer/0","maxResults": 25}
The custom adapter inspects field names and aliases for common parcel, situs, owner, assessment, appraisal, tax, and building fields. If it cannot identify the field required by the selected search mode, the run stops with an actionable diagnostic and does not fabricate results.
Output example
{"recordId": "dentonCountyTx:R111625","county": "Denton County","state": "TX","parcelNumber": "R111625","alternateParcelNumber": "111625","propertyAddress": "5 WOODHAVEN CT","ownerName": "MITCHELL, JUNIOR R","ownerMailingAddress": "5 WOODHAVEN CT, KRUGERVILLE, TX 76227","legalDescription": "TIMBER MESA BLK C LOT 5","propertyUse": "Real, Residential, Single Family","yearBuilt": 1986,"squareFeet": 1547,"landAreaSqFt": 15008,"landAreaAcres": 0.344536,"assessedLandValue": 25656,"assessedImprovementValue": 106320,"assessedTotalValue": 131976,"appraisedValue": 131976,"taxableValue": null,"taxAmount": null,"taxArea": "C18, CAD, G01, S02","exemption": "HS","rollYear": null,"latitude": null,"longitude": null,"sourceName": "Denton County public parcel layer","sourceUrl": "https://services.arcgis.com/9dTWrhPzuDPnUVXr/ArcGIS/rest/services/County_Parcels/FeatureServer/0","retrievedAt": "2026-09-07T12:00:00.000Z"}
The default dataset contains only normalized property records. OUTPUT in the default key-value store records whether the run returned DATA, a truthful EMPTY result, a user-input REJECTED diagnostic, or a source BLOCKED/FAILED diagnostic.
Pricing
This Actor uses pay-per-event pricing. These are the current Apify Store event prices:
| Event | Price (USD) | When it is charged |
|---|---|---|
apify-default-dataset-item | FREE: $0.049; BRONZE: $0.049; SILVER: $0.049; GOLD: $0.043; PLATINUM: $0.043; DIAMOND: $0.043 | Property record — One normalized, schema-valid county property record written to the default dataset. |
apify-actor-start | $0.005 | Actor Start — Charged when the Actor starts running. Number of events charged depends on Actor memory (one event per GB, minimum one event). — Charged once per run. |
Apify platform usage for this Actor run is included alongside the event prices above; no separate per-run platform-usage fee is passed to users.
This covers Apify platform usage for this Actor run. Other Apify products or usage outside this Actor run may still follow your account plan.
Reliability and limits
The Actor uses direct public ArcGIS metadata and query endpoints, bounded 30-second requests, three attempts with exponential backoff for transient failures, source pagination, record normalization, and stable-ID deduplication. HTTP access denials, upstream failures, unsupported field mappings, and honest no-match results are classified separately in OUTPUT.
The Actor does not bypass authentication, CAPTCHAs, paywalls, access controls, or county publication restrictions. A custom layer must allow anonymous HTTPS queries. Large wildcard exports are intentionally not offered; searches require a specific query and return at most 500 records.
Data use and privacy
Property records may contain personal information that is lawful to access but sensitive in context. Use the data only for a legitimate purpose and follow applicable privacy, fair-housing, consumer-reporting, solicitation, and public-record laws. Do not use this Actor to make eligibility, credit, housing, employment, insurance, or other high-impact decisions without appropriate legal review and authoritative verification. Source data is informational and can be stale, incomplete, or incorrect; confirm material facts with the relevant assessor, appraisal district, or tax office.
Support
For a failed custom layer, include the public layer URL, selected search mode, and redacted OUTPUT diagnostic. Do not send private tokens, cookies, or personal credentials.