har.com APIwww.har.com ↗
Retrieve active listings and past transactions for Houston real estate agents on HAR.com, including prices, property details, beds/baths, and sold dates.
curl -X GET 'https://api.parse.bot/scraper/11c10551-f94a-4d12-916c-30a8e0e3362e/get_agent_listings?agent_id=jsmith§ions=Recently+Sold&agent_slug=john-smith' \ -H 'X-API-Key: $PARSE_API_KEY'
Get all active listings and past transactions for a HAR.com real estate agent. Returns data across sections: For Sale, For Rent, Recently Sold, Recently Rented, and Recent Showings. Each listing includes address, zip code, price, status, property type, beds/baths/sqft, and for sold/rented properties: who the agent represented (Buyer/Seller) and the transaction date.
| Param | Type | Description |
|---|---|---|
| agent_id | string | Agent ID used in HAR URLs (e.g., 'jsmith' from listings_jsmith). |
| sections | string | Comma-separated list of sections to include. Accepted values: 'For Sale', 'For Rent', 'Recently Sold', 'Recently Rented', 'Recent Showings'. Empty string returns all sections. |
| agent_slug | string | Agent URL slug used in HAR profile URLs (e.g., 'john-smith' from har.com/john-smith/...). |
{
"type": "object",
"fields": {
"agent_id": "string - Agent ID used",
"sections": "object - Keys are section names (for_sale, for_rent, recently_sold, recently_rented, recent_showings), values are arrays of listing objects with address, zip_code, price, status, property_type, beds, full_baths, half_baths, sqft, mls_number, listing_id, and optionally represented, listed_price, sold_date or rented_date",
"agent_name": "string - Agent's display name",
"agent_slug": "string - URL slug used",
"total_listings": "integer - Total number of listings across all returned sections"
},
"sample": {
"data": {
"agent_id": "johndoe",
"sections": {
"for_sale": [
{
"beds": "4",
"sqft": "3,741",
"price": "$635,000",
"status": "Active",
"address": "123 Main St, Springfield, IL 62704",
"section": "For Sale",
"zip_code": "62704",
"full_baths": "3",
"half_baths": "1",
"listing_id": "10821183",
"mls_number": "3853180",
"property_type": "Single-Family"
}
]
},
"agent_name": "John Doe",
"agent_slug": "john-doe",
"total_listings": 10
},
"status": "success"
}
}About the har.com API
The HAR.com API exposes 1 endpoint — get_agent_listings — that returns up to five categories of listing data for any agent on the Houston Association of Realtors platform. A single call can return active For Sale and For Rent listings, Recently Sold and Recently Rented transactions, and Recent Showings, each with address, price, property type, beds, baths, square footage, and sale dates. The response covers both current inventory and historical transaction records tied to a specific agent.
What the API Returns
The get_agent_listings endpoint retrieves all publicly visible listing activity for a HAR.com agent. The response object includes agent_name, agent_id, agent_slug, and total_listings, plus a sections object whose keys map to the five data categories: for_sale, for_rent, recently_sold, recently_rented, and recent_showings. Each section contains an array of listing objects with fields such as address, zip code, price, status, property type, beds, baths, and square footage. Sold and rented records additionally carry transaction dates and the represented party (buyer or seller).
Input Parameters
You can identify an agent using either agent_id (the short identifier appearing in HAR listing URLs, e.g. jsmith from listings_jsmith) or agent_slug (the profile URL segment, e.g. john-smith from har.com/john-smith/...). At least one of these two identifiers is required. The optional sections parameter accepts a comma-separated list of section names — For Sale, For Rent, Recently Sold, Recently Rented, Recent Showings — so you can limit responses to only the data categories you need rather than fetching all five every time.
Coverage and Scope
HAR.com is the listing platform for the Houston Association of Realtors, so geographic coverage is specific to the Greater Houston area and surrounding markets served by HAR member agents. The API reflects the agent's public-facing activity: current listings under their name and historical transactions where they represented a party. The total_listings field in the response gives a quick count across all returned sections without iterating arrays.
- Comparing an agent's active inventory count against their historical sold volume to evaluate production levels.
- Tracking price points and property types in an agent's
recently_soldsection to understand their typical deal profile. - Aggregating
for_rentandrecently_renteddata for agents who specialize in Houston rental markets. - Building agent profile pages that display current listings alongside transaction history using address, price, and status fields.
- Monitoring
recent_showingsdata to identify agents with active buyer-side activity in specific zip codes. - Filtering by
sections=Recently Soldto pull only closed transaction records for market analysis without fetching active listings. - Validating agent representation history (buyer vs. seller) for due diligence in vendor selection.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 250 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does HAR.com offer an official developer API?+
What does the `sections` parameter actually filter, and what happens if I omit it?+
sections is omitted, the response includes all five categories: for_sale, for_rent, recently_sold, recently_rented, and recent_showings. Passing a comma-separated value like Recently Sold,For Sale restricts the sections object to only those keys, which reduces payload size when you only need a subset of an agent's activity.Does the API return agent contact information such as phone number, email, or brokerage name?+
agent_name, agent_id, and agent_slug, but does not expose phone numbers, email addresses, or brokerage affiliation fields. You can fork this API on Parse and revise it to add an agent profile endpoint that captures those fields.Is coverage limited to Houston, and can I use this for other Texas markets?+
Does the API support pagination for agents with large transaction histories?+
total_listings field indicates the full count returned. If you need paginated access or deeper historical archives beyond what HAR.com exposes publicly, you can fork the API on Parse and revise it to add pagination logic.