Count of sold properties in a ZIP in the last 365 days

GET /api/properties/sold/count-by-zip/

1 credit

What it returns

Just the count of residential properties sold in a ZIP within the last 365 days. Same dedup + recency rules as sold-by-zip, but only the integer count — useful when you don't need the property details and want to minimize cost.

When to use it

• Display market velocity in a header widget (no need to render rows).
• Drive a chart of monthly sales trend across many ZIPs cheaply.
• Pre-check whether a ZIP has enough comp activity before calling sold-by-zip.

Date range

By default the endpoint returns the full trailing 365 days. Pass start_date, end_date, or both (YYYY-MM-DD) to narrow that to a specific window — for example one calendar month at a time instead of re-pulling the whole year on every poll:

Both bounds are optional and inclusive, and both are independent: pass only start_date for an open-ended window, or only end_date to cut off recent sales. Passing neither leaves existing behaviour unchanged.

Either bound must fall within the last 365 days. An older date returns 400 naming the earliest date we can serve, rather than quietly returning a partial set.

Pricing

1 credit per call regardless of the count.

FAQ

What's the difference between this and sold-by-zip?

This returns one integer (1 credit). sold-by-zip returns the full list (1 credit per 20 properties). Use this for cost-efficient screening; use sold-by-zip when you need details.

Parameters

• zip (query, required) — 5-digit US ZIP code.
• start_date (query) — Earliest sale date to include, as YYYY-MM-DD. Optional — omit for the full 365-day window. Inclusive: a sale on this exact date is returned. Must fall within the last 365 days; anything older returns 400, since that is the whole window we retain.
• end_date (query) — Latest sale date to include, as YYYY-MM-DD. Optional — omit for no upper bound. Inclusive: a sale on this exact date is returned. Must be on or after start_date and within the last 365 days.

Responses

• 200
• 400 — Bad request — a required parameter is missing or failed validation. Costs 0 credits.
• 401 — Authentication failed — missing or invalid API key. Costs 0 credits.
• 402 — Payment required — no active subscription or insufficient credit balance. Costs 0 credits.
• 503 — Upstream data provider is temporarily unavailable — retry with backoff.

More in Market Data

• List residential properties sold in a ZIP in the last 365 days — GET /api/properties/sold/by-zip/
  Every residential property sold in a given US ZIP code within the last 365 days, with sale date, sale price, coordinates, and basic property characteristics (bed/bath, square footage, year built, lot size).
• Mortgage and lien data for a US property — GET /api/mortgage-lien/analysis/
  Mortgage and lien records for a US property — current and historical mortgages, lien summary, involuntary liens, pre-foreclosure status, and data quality metadata.