GET /api/v1/feed/listings pages through the full file of US rental listings a customer is licensed to show in their product, 500 listings a page.
curl -H "Authorization: Bearer $HOUSINGFEED_KEY" "https://housingfeed.com/api/v1/feed/listings?version=2026-10-19&page=1"
| Parameter | Meaning |
|---|---|
version | Optional. Defaults to the current version. Pin it for a whole pass so pages cannot shift under you. |
page | Optional, from 1. Follow next until it is null. |
{
"version": "2026-10-19",
"page": 1,
"pages": 24,
"listing_count": 12000,
"listings": [
"{ listing }",
"..."
],
"next": "/api/v1/feed/listings?version=2026-10-19&page=2"
}
500 listings per page, ordered by uid. Each listing carries these fields; your sample shows any additional detail fields agreed for your feed.
| Group | Fields |
|---|---|
| Identity & source | uid, listing_id, url |
| Location | address, street, city, state, zip, lat, lng |
| Rent | rent_min, rent_max, rent_usd |
| Property | beds, baths, sqft_min, sqft_max, property_type, furnished |
| Availability & content | available, image, n_photos, description, amenities |
| Verification | last_seen_at |
Missing values are null, not zero. Zero bedrooms means a studio. Keep ZIP codes as strings.
Read every page of one version once. After that, apply weekly changes instead of re-reading the file.
Tell us your cities and what you are building. You get a sample in the production format and the listing count for your markets, usually within one business day.
Request a sample