An API and weekly feed of US rental listings collected where property managers publish them, licensed for display in your product. One schema, stable ids, delistings delivered. Nothing to crawl, nothing to maintain.
700,000+ listings from 75,000+ property-manager sites across 51 states. Measured 2026-09-14. Licensed for display with attribution and a link back to the source. Licence terms
| Route | Rights to display | Freshness | What you get | Fits |
|---|---|---|---|---|
| Portal API (Zillow Bridge, Apartments.com partner feeds) | Partner programmes with their own terms; not a licence for a small product | Good | The portal's inventory, on the portal's conditions | Large partners the portal chooses |
| Scraping a portal | None: the portal's terms do not permit reuse, and the leads belong to the portal | Only as fresh as the scrape | A copy of someone else's marketplace, blocked and rebuilt every quarter | Research, never display |
| MLS / IDX feeds | Broker licence per MLS, sale-heavy, rentals thin outside condo markets | Good | Broker-listed rentals only | Brokerages |
| Source-direct feed (HousingFeed) | Licensed for display with attribution and a link back to the manager's page | Re-verified weekly at the source; delistings delivered | Manager-published listings in one schema: address, rent, beds, photos, availability, source URL | Products that show rentals to users |
What "displayable" means here: each listing was collected from the property manager's own site or leasing software, is licensed to you for display in your consumer-facing product, and asks three things of you: name the manager as the source, link the listing back to its page, and send enquiries to the manager. No revenue share, no exclusivity. Read the standard terms →
Type a state or metro for the current count of displayable listings, verified at the source within 30 days. Your sample shows the exact number for your ZIPs.
Address and coordinates, rent, bedrooms, bathrooms, size, availability, photos, description, amenities, property type, the manager's own listing URL, when we first saw it and when we last verified it.
HousingFeed{
"id": "appfolio:sigmanrealestatepartnersllc:12",
"platform": "appfolio",
"url": "https://sigmanrealestatepartnersllc.appfolio.com/listings/detail/98639f6a-831c-4d70-8784-4a618eaaa559",
"address": "519 Asbury Ave - A, Asbury Park, NJ 07712",
"street": "519 Asbury Ave - A",
"city": "Asbury Park",
"state": "NJ",
"zip": "07712",
"country": "US",
"lat": 40.219562498814,
"lng": -74.007707051157,
"rent_min": 3300,
"currency": "USD",
"rent_usd": 3300,
"beds": 3,
"baths": 1,
"sqft_min": 923,
"property_type": "apartment",
"available": "10/1/26",
"image": "https://images.cdn.appfolio.com/sigmanrealestatepartnersllc/images/7cef1482-578f-4620-a8f4-634e22fa87a7/medium.jpeg",
"images": [
"https://images.cdn.appfolio.com/sigmanrealestatepartnersllc/images/7cef1482-578f-4620-a8f4-634e22fa87a7/medium.jpeg",
"https://images.cdn.appfolio.com/sigmanrealestatepartnersllc/images/7cef1482-578f-4620-a8f4-634e22fa87a7/large.jpeg",
"... 18 more"
],
"amenities": [
"cats allowed",
"small dogs allowed"
],
"description": "Welcome to 519 Asbury Ave, a beautifully appointed 3-bedroom, 1-bathroom first-floor apartment offering comfort, convenience, and easy moder...",
"first_seen_at": "2026-09-08T12:33:47+00:00",
"last_seen_at": "2026-09-11T13:29:13+00:00",
"scraped_at": "2026-09-11T13:29:13+00:00"
}id is stable across runs. Dedupe on it, diff on it, and never see the same unit under three names.
first_seen_at and last_seen_at on every record. A unit leaves the feed only when its source stops publishing it, and it arrives in your next delta as a removed record.
Weekly export of added, changed and removed records, or incremental pulls with newSinceDays. The same 36 fields in the same order for every source. Docs →
Field coverage varies by source and market; your sample shows the exact share. Full field coverage →
In the feed: listings property managers and owners publish on their own sites and leasing software, from the small landlord's management system to the leasing sites of large operators. Not in the feed: anything that originates on a consumer portal, including units individual landlords list only there. In some coastal, condo-heavy metros that is most of what a portal shows, and manager-direct coverage is thinner. Your market check and your sample show the real number before you decide. Coverage by state, metro and source category →
Within one business day: a real export for your cities in the schema you would license, the displayable-listing count and field coverage for your geography, and the price for that scope.
You will have the export and the coverage numbers within one business day.
Most teams book a short call to walk through coverage for their exact ZIPs, field completeness, and how the weekly deltas fit their stack.
Book 20 minutesOr just reply to the sample email.
From $300 a month for a metro, quoted per scope on your sample; regional and national scopes on the same basis. Month to month, 30 days' notice, the first 30 days free once you decide to integrate. No revenue share, no exclusivity.
Type any state or metro into the market check on this page for the current displayable count. Your sample gives the exact number for your ZIPs and the share of records with photos, coordinates and availability.
Yes, in your own consumer-facing products, with attribution and a link back to each listing's source page. The standard licence terms are public and versioned.
No. Portal listings are not ours to license for display. The feed is collected from property managers' own websites and leasing software, which is why it can be shown in your product. Why there is no Zillow rental API, and what to use instead →
Each listing is re-checked against its source weekly. When the source no longer lists it, the record is marked delisted and appears in the removed set of your next delta. A failed request never removes a listing; only the source does.
Yes: the docs show one POST with your filters as JSON and the same 36-field rows back, plus newSinceDays for incremental pulls. The sample is the exact schema you would license, so the integration you build against it is the one you ship.
The Display Feed is United States today. The Data API also carries portal-derived data for 30 countries, for research and internal use, without display rights.
Building a research tool or an internal dataset instead? The real estate API serves the whole database, portals and 30 countries included, pay per row, without display rights.