POST
Hide listing

Overview

Sets the caller’s listing status from LIVE to HIDDEN. A hidden listing is excluded from match candidate generation and does not appear in other users’ match feeds, but is preserved in the database and any existing matches/conversations remain intact. Only LIVE listings can be hidden. Calling this on a DRAFT listing (never published) or a listing that is already HIDDEN returns 409 STATE_CONFLICT — the server refuses the redundant transition rather than silently no-op’ing so the client can detect drift. To re-list a hidden listing, call POST /current-home/me/publish. The publish eligibility gate still applies (onboarding complete + tenancy approved + at least one photo + 50..150-char description).

Authentication

Bearer <accessToken> required. Scope: user.

Path parameters

None.

Query parameters

None.

Request body

None.

Response — 200 OK

Returns the updated Home object with status = HIDDEN.

Error responses

Example error — 409

Side effects

  • Sets current_homes.status = "HIDDEN" on the caller’s listing.
  • updatedAt is bumped.
  • Hidden listings are filtered out of the match-candidate query (Phase 3 worker honours this flag).
  • Enqueues a match.recompute job for the owner to drop stale match rows (Phase 3 worker; stub in Phase 2).
  • Existing matches and conversations are preserved.

See also

curl