AMH Properties and Details Scraper

What does AMH Properties and Details Scraper do?

This Actor is designed to normalize AMH Homes rental-search results into structured property records. It reads supported result data embedded in the search page and attaches a matching official property detail URL when that link is present. It does not open individual property pages. AMH's Terms and Conditions section 5 prohibits spiders, robots, and extraction tools except normal browser use, and limits copying of site material. The Actor is therefore permission-gated and makes zero source requests by default. Live collection is not qualified.

Why use AMH Properties and Details Scraper?

If you have written authorization that covers automated collection and reuse, the Actor can deduplicate properties, group details into location, rent, property, availability, tour, media, application, and contact objects, and retain source provenance. Each property row represents values exposed in the search-page payload; the Actor does not claim to retrieve a complete individual detail page. Apify provides run history, scheduling, dataset exports, API access, and integrations. The Actor does not use proxies, log in, or work around access controls.

What data can AMH Properties and Details Scraper extract?

Optional values are emitted only when present in the supported page data and are omitted when absent.

Group	Example fields
Identity	Property ID/number, title when present, canonical listing URL
Location	Street, city, state, ZIP code, latitude, longitude
Rent	Rent and total rent when present, availability date
Property details	Bedrooms, bathrooms, square feet, year built, description, features
Amenities and media	Public amenities, image references, image count
Access and tours	Application availability, self-tour flags, virtual-tour URL
Contact and provenance	Public phone field when present, source URL, extraction method, timestamp

How to scrape AMH Homes

1. Review the current AMH terms and obtain written authorization for automated collection and use of property data.
2. Set Current written permission confirmed only after that authorization exists. The checkbox is an operator attestation and does not grant permission.
3. Add one or more exact official amh.com/query URLs covered by the authorization.
4. Set the global record limit and request pacing within the authorization.
5. Inspect dataset rows and the OUTPUT summary. A successful process status does not prove source records were available.

How much will it cost to use AMH Properties and Details Scraper?

Apify resource costs depend on account pricing and the actual run shown in Console; this Actor makes no fixed-price promise. Its default input uses no AMH request. Once authorized, each run checks robots.txt and then requests supplied query pages. More URLs and larger pages use additional network time and compute. requestDelayMs adds a fixed wait before each query request. There is no proxy use, pagination loop, or automatic retry.

Input

See the input tab for the complete configuration. The schema rejects unknown properties, fixture inputs, and debug controls.

Property	Type	Default	Range or behavior
authorizationConfirmed	boolean	false	Attestation that current written permission covers automated collection and use.
startUrls	array of { "url": "..." }	[]	Up to 10 explicit official AMH HTTPS query URLs. No search is generated by default.
maxItems	integer	25	1–1,000 unique property rows across all input URLs.
requestDelayMs	integer	1000	0–10,000 ms before each authorized query request.
timeoutSecs	integer	30	5–120 seconds per request.

The default input finishes successfully as a policy skip, with zero source requests and no dataset rows:

{}

Input shape to use only after current written authorization covers the query URL and data use:

{
  "authorizationConfirmed": true,
  "startUrls": [
    { "url": "https://www.amh.com/query?criteria=Charlotte%2C%20NC" }
  ],
  "maxItems": 25,
  "requestDelayMs": 1000,
  "timeoutSecs": 30
}

Output

You can download the dataset in various formats such as JSON, HTML, CSV, or Excel.

The abbreviated property row below is synthetic schema documentation and is not current AMH data:

{
  "recordType": "amh-property",
  "recordId": "amh:illustrative-id",
  "actorRank": 3421,
  "actorName": "AMH Properties and Details Scraper",
  "actorSlug": "amh-properties-and-details-scraper",
  "sourceActorName": "AMH Crawler",
  "sourceActorSlug": "ugreen/amh-crawler",
  "sourceActorUrl": "https://apify.com/ugreen/amh-crawler",
  "status": "succeeded",
  "dataAvailable": true,
  "propertyId": "illustrative-id",
  "propertyNo": "SYNTHETIC-1",
  "title": "Illustrative rental home",
  "addressLine1": "1 Example Street",
  "city": "Example City",
  "state": "NC",
  "zipCode": "00000",
  "rent": 2000,
  "bedrooms": 3,
  "bathrooms": 2,
  "unitSqFt": 1500,
  "location": { "city": "Example City", "state": "NC" },
  "rentalDetails": { "rent": 2000 },
  "propertyDetails": { "bedrooms": 3, "bathrooms": 2, "unitSqFt": 1500 },
  "media": { "imageUrls": [], "imageCount": 0 },
  "sourceUrl": "https://www.amh.com/query?criteria=example",
  "sourceDomain": "www.amh.com",
  "sourceWebsite": "amh.com",
  "sourceBlocked": false,
  "extractionMethod": "nextjs-page-props",
  "scrapedAt": "2026-09-25T00:00:00.000Z"
}

The default run's OUTPUT summary is shown below. status reports the overall Actor outcome as SUCCEEDED; runStatus records SKIPPED_POLICY; and collectionStatus explains that collection was skipped by the authorization gate. Failures and blocked requests are logged and reflected as FAILED when no real property records were saved. No error or placeholder records are written to the dataset.

{
  "recordType": "amh-summary",
  "actorRank": 3421,
  "actorName": "AMH Properties and Details Scraper",
  "actorSlug": "amh-properties-and-details-scraper",
  "sourceActorName": "AMH Crawler",
  "sourceActorSlug": "ugreen/amh-crawler",
  "sourceActorUrl": "https://apify.com/ugreen/amh-crawler",
  "status": "SUCCEEDED",
  "runStatus": "SKIPPED_POLICY",
  "collectionStatus": "SKIPPED_POLICY",
  "authorizationStatus": "AUTHORIZATION_REQUIRED",
  "authorizationConfirmed": false,
  "sourceUrls": [],
  "propertyCount": 0,
  "itemCount": 0,
  "uniqueRecordCount": 0,
  "requestCount": 0,
  "responseBytes": 0,
  "robotsBlocked": 0,
  "cloudOperations": 0,
  "finishedAt": "2026-09-25T00:00:00.000Z"
}

The OUTPUT key-value record summarizes authorization status, requests, property count, bytes, robots blocks, and completion time. A valid empty source search is SUCCEEDED with zero rows. If an error occurs after real property rows are saved, the Actor remains SUCCEEDED with collectionStatus: "PARTIAL" and the saved-row count. A failure before any real record is saved is FAILED.

Tips and advanced options

maxItems is global across all input URLs. Duplicate records are removed using a stable property identity. The Actor does not build searches from city criteria or paginate automatically; provide explicit authorized query URLs. It checks robots.txt before querying, refuses redirects, and retains no fabricated row when a page is empty or blocked. Contact and tour values are optional and are emitted only if present in supported page data.

FAQ, support, and responsible use

AMH Terms §5 limits use of its services to leasing-related purposes and prohibits spiders, robots, and extraction or navigation tools other than normal browser use. Do not run this Actor without separate written authorization that covers the activity and reuse. Robots.txt allowance does not override the Terms. This Actor is not affiliated with AMH. Respect current terms, robots instructions, privacy requirements, and applicable law; do not collect personal data without a legitimate reason. Submit bugs or feature requests in the Actor's Issues tab with a run ID and diagnostic summary where possible.

For offline checks, run npm test, npm run check, npm run validate, and apify validate-schema. The default policy run writes only the summary with zero source requests; saved run output does not qualify the current build as a live scraper.

Storage and dependency remediation

This stateless HTTP Actor uses Apify’s documented default Dataset/KVS REST endpoints on Cloud and the standard local filesystem layout for isolated apify run checks. The runtime token stays in an authorization header sent only to api.apify.com; it is never logged or sent to the target source. A small readable src/platform.js adapter replaces the SDK storage-only usage, removing the Crawlee/cache/ZIP/proxy dependency graph with unpatched advisories. Storage operations are awaited and fail explicitly; uncertain dataset writes are not retried. No migration, queue, proxy or general SDK features are advertised. Source authorization gates, access boundaries and data contracts are unchanged. Node 24 is required. Run npm ci, the existing regression tests (including platform storage tests), schema checks and a production-graph audit before deployment.