ListingData.

OUR PUBLIC DATA BOUNDARY

Enough to build with.
Considered by design.

ListingData offers a limited public projection of source listing data. The same field rules apply to REST, search, aggregate endpoints and MCP tools.

✓

IN THE PUBLIC VIEW

Useful market facts

  • Public address and location fields, where supplied
  • Property type and source-supplied bed, bath and car counts
  • Observed listing status and available timestamps
  • Advertised marketing price text and recorded text changes
  • Agency identifiers and agency names
  • Bounded market counts based on the available records
−

ALWAYS WITHHELD

Private & proprietary fields

  • Full property descriptions and description-derived search
  • Internal numeric search prices and search bands
  • Agent contact email addresses and telephone numbers
  • Private contacts, account records and internal operational data
  • Hidden source fields or unrestricted raw database documents
  • Fields outside the documented public schema

SAME RULES, EVERY INTERFACE

No back door
through another endpoint.

The API returns documented fields from an explicit public projection. Search and MCP do not grant access to full source documents. Numeric internal price filters, descriptions and agent contact searches are not part of the public query surface.

Agency name does not mean contact access

An agency’s name is a useful market attribution. It does not include access to private contact channels. ListingData does not provide an agent email or phone directory.

Marketing price is different from search bands

Marketing price text is what the listing advertises, where that observation is available. Search prices and internal price bands are operational fields and remain excluded, including from sorting, filtering and generated examples.

Open access is not an unrestricted data licence

A free account provides bounded access to the documented service. It does not grant permission to reconstruct the underlying database, bypass usage limits or redistribute data without regard to source rights. Read the service terms.

Build with the documented contract

Use the response schema and handle null values. Do not infer that a field exists because a source website contains it. Do not use or redistribute an unexpected private field. The documented public contract defines the information your integration may use.