Buildium Scraper — US Rentals + Email & Phone from Any PM Site
Pricing
from $1.00 / 1,000 results
Buildium Scraper — US Rentals + Email & Phone from Any PM Site
Turn any Buildium / ManageBuilding rentals URL into live vacancies with office email and phone. Public MITS XML: rent, beds, baths, photos, apply URL, Email, PhoneNumber. One GET per manager. HTTP only, no login. JSON, CSV or Excel. You bring the PM URL — not a weekly dump.
Pricing
from $1.00 / 1,000 results
Rating
0.0
(0)
Developer
Muhamed Didovic
Maintained by CommunityActor stats
0
Bookmarked
17
Total users
16
Monthly active users
7 days ago
Last modified
Categories
Share
Turn any Buildium / ManageBuilding rentals URL into structured vacancies — including office email and phone. Paste https://{tenant}.managebuilding.com/Resident/public/rentals. The actor hits that manager's public MITS XML feed (one GET) and returns rent, beds, baths, photos, apply URL, email, and phone.
Why Use This Scraper?
- Public XML, not HTML archaeology. Buildium documents
XMLRentals.ashxas the listing feed. We use it. - Email and phone in the feed. HousingFeed's Buildium dump ships listing facts only. The XML includes
<Email>and<PhoneNumber>. - One request per manager. No pagination crawl, no browser.
- URL-in. You choose the property manager. Not a weekly national snapshot.
- Apply URL included.
{origin}/Resident/rental-application/new/apply?listingId=…
Overview
One dataset row per advertised floorplan/listing in that tenant's public feed. Typical use: you already have ManageBuilding URLs (from a PM directory, a website, or a client) and want inventory + contacts. There is no "all Buildium in Texas" search — you need origins.
Supported Inputs
| Input | What it is | Example |
|---|---|---|
| Public rentals page | HTML list | https://zoulproperties.managebuilding.com/Resident/public/rentals |
| XML feed | Direct MITS URL | https://zoulproperties.managebuilding.com/Resident/PublicPages/XMLRentals.ashx |
startUrl | Single-URL convenience field | same as one startUrls item |
The actor rewrites any origin to /Resident/PublicPages/XMLRentals.ashx (Buildium 301s that to /resident/api/public/listingFeeds).
Unsupported: authenticated api.buildium.com (needs client id/secret), tenant login portals, and city-wide search with no URL.
Seed list: this repo ships seeds/start-urls.json — ~526 {tenant}.managebuilding.com/Resident/public/rentals URLs mined from Common Crawl and live-checked against the public XML feed.
Use Cases
| Audience | What they get |
|---|---|
| Rental lead-gen | Office email + phone for managers you already have URLs for |
| PropTech / aggregators | Inventory that never syndicated to Zillow |
| Researchers | Asking rents and unit mix for a named manager |
| Agencies | A dump of one competitor's public vacancies |
How It Works

- Paste one or more ManageBuilding rentals (or XML) URLs.
- The actor fetches that origin's public MITS XML feed.
- Each
<Floorplan>becomes a dataset row (rent, beds, photos, contacts). - It stops at
maxItems.
Input Configuration
| Field | Type | Default | What it does |
|---|---|---|---|
startUrls | string list | sample NE manager | Rentals page or XML URL |
startUrl | string | empty | Same, for a single URL |
maxItems | integer | 100 | Cap on saved listings (free accounts hard-capped at 100) |
includeInactive | boolean | false | ?listings=all — active + inactive |
proxy | proxy object | off | Optional |
Example — one manager, 25 listings
{"startUrls": ["https://zoulproperties.managebuilding.com/Resident/public/rentals"],"maxItems": 25}
Example — two managers, include inactive
{"startUrls": ["https://zoulproperties.managebuilding.com/Resident/public/rentals","https://wisechoiceproperties.managebuilding.com/Resident/public/rentals"],"includeInactive": true,"maxItems": 200}
Output Overview
Each row is one public listing. Email/phone come from the property's XML <Address><Email> and <Phone><PhoneNumber> (and management-level contacts when present).
Output Samples
URL https://zoulproperties.managebuilding.com/Resident/public/rentals:
{"platform": "buildium","id": "buildium:zoulproperties:115843","listingId": "115843","tenant": "zoulproperties","url": "https://zoulproperties.managebuilding.com/Resident/public/rentals/115843","title": "Royal Prince - 7A","address": "311 North Lincoln Avenue - 7A, Grand Island, NE, 68801","city": "Grand Island","state": "NE","zip": "68801","rent": 950,"beds": 1,"baths": 1,"sqft": 550,"email": "inquiries@grandislandrealty.net","phone": "308-382-4247","officeName": "Grand Island Realty","applyUrl": "https://zoulproperties.managebuilding.com/Resident/rental-application/new/apply?listingId=115843"}
Key Output Fields
| Group | Fields |
|---|---|
| Identity | platform, id, listingId, propertyId, tenant, url |
| Listing | title, description, rent, rentMin, rentMax, deposit, beds, baths, sqft, propertyType, unitCount |
| Location | address, street, city, state, zip |
| Media | image, images[], amenities[] |
| Contact | officeName, email, emails[], phone, phones[], applyUrl |
| Meta | currency, scrapedAt |
latitude / longitude are reserved and currently null — the MITS feed we probed did not include coordinates.
FAQ
Can I scrape all Buildium listings in a state without URLs? Not from Buildium itself. Use seeds/start-urls.json (~526 live-checked ManageBuilding origins) or housingfeed/buildium-scraper if you want a pre-built geo DB instead of live URL-in.
Is the XML allowed? Buildium publishes it for websites to embed listings (help.buildium.com → "Rental listings in XML"). We only read that public feed.
Why might email be empty? Some managers leave <Email /> blank in the feed. Phone can still be present.
Do I need API keys? No. api.buildium.com is a different, authenticated product.
Support
Open an issue on the actor page.
Additional Services
Need a geo-filtered cut of the seed list, a combined AppFolio+Buildium run, or a private feed? Use the issues tab or memo23's profile. Raw seeds: seeds/ in this repo.
Explore More Scrapers
- AppFolio Scraper — URL-in AppFolio listings + office phone
- Apartments.com Scraper
- Zumper Scraper
- Zillow Scraper
- More at apify.com/memo23
🤖 For AI Agents & LLM Apps
Compact reference for agents calling this actor via the Apify MCP server or the Apify API (memo23/buildium-scraper).
Purpose: Live-scrape rental vacancies from a Buildium/ManageBuilding public rentals URL via the MITS XML feed, including office email and phone.
Minimal input:
{"startUrls": ["https://zoulproperties.managebuilding.com/Resident/public/rentals"],"maxItems": 25}
Output fields: platform, id, listingId, propertyId, tenant, url, title, description, address, street, city, state, zip, latitude, longitude, rent, rentMin, rentMax, currency, deposit, beds, baths, sqft, propertyType, unitCount, amenities, image, images, officeName, email, emails, phone, phones, applyUrl, scrapedAt.
Behaviors an agent should know:
- Always set
maxItems. Default 100; free accounts capped at 100. - Requires a
*.managebuilding.comrentals or XML URL. No city-wide search. includeInactive: truefetches?listings=all.- Coordinates are currently null.
- Proxy off by default.
⚠️ Disclaimer
This Actor is an independent tool and is not affiliated with, endorsed by, or sponsored by Buildium, RealPage, Inc., or any of their subsidiaries. All trademarks mentioned are the property of their respective owners.
The scraper accesses only the publicly documented rental-listing XML feed and public rentals pages on *.managebuilding.com — no authenticated Buildium Open API, tenant records, or content behind a login. Users are responsible for ensuring their use complies with Buildium's Terms of Service, applicable data-protection law (GDPR, CCPA, etc.), and any contractual obligations of their own organization.
SEO Keywords
buildium scraper, managebuilding scraper, buildium listings api, scrape buildium, buildium rental listings, XMLRentals.ashx, MITS rental feed, property manager listings scraper, US rental scraper, buildium email, buildium phone, off-market rentals scraper, property management inventory, buildium data extraction, RealPage listings