Natural Language In, Evidence Out

A renter types what they actually want. The search API parses it into structured constraints, searches your own listing index, and returns each match with the reasons it matched — not just a similarity score you have to take on trust.

🔍 Search API

What it does

  • Natural language query understanding, not just keyword matching
  • Hybrid and semantic search over your own listing index
  • Match-reason evidence returned alongside every result
  • A partitioned, HNSW-indexed store per tenant
POST /v1/search
curl -sS -X POST https://api.thepropertystack.com/v1/search \
  -H "Authorization: Bearer $PROPERTYSTACK_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "query": "3 bedroom within 40 minutes of University of Cape Town",
  "limit": 20,
  "options": { "include_fields": true, "explain": true }
}'
Default

Ids and evidence back

A search returns each match's doc_id, score and match reasons — you look the rest up in your own database, so a stale index can never show a renter the wrong price.

include_fields: true

Or the listing fields directly

Set one option on the search request and price, bedrooms, bathrooms and location come back inline — no lookup needed, for a thin client that would rather not hydrate.

Search works on the listings you send us — see how listings get in — and understands commute constraints through the geo API.

Try a Search Against Real Listings

The public sandbox runs the same API against a demo catalogue. No account needed.

See It In ActionTalk to Sales

Or email us directly at info@thepropertystack.com