Market routes expose classified listings and supporting aggregates (references, facets, summaries). Request bodies and response envelopes are defined in the API reference.

​
Entry points

  • POST /v2/market/listings/search — Primary discovery surface with structured filters.
  • GET /v2/market/listings/{listing_id} — Single listing detail.
  • POST /v2/market/references/search — Reference-centric lookups.
  • POST /v2/market/summary — Aggregate slices suitable for dashboards.
  • POST /v2/market/facets — Facet buckets aligned with search filters.
Filter vocabulary aligns with saved views / message-feed dimensions where possible (brand, reference, condition, geography, price bands, etc.) — exact enums live in OpenAPI.

​
Mental model

Listings are derived from WhatsApp-sourced messages that passed classification. Until classification data exists for a thread, market rows may be sparse or absent — integrate defensively and rely on HTTP/status semantics from the contract.