Hide listing
Current Home
Hide listing
Switch the caller’s LIVE listing to HIDDEN (paused — no new matches).
POST
Hide listing
Overview
Sets the caller’s listingstatus 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 + 100..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 withstatus = HIDDEN.
Error responses
| Status | Code | Meaning |
|---|---|---|
| 401 | UNAUTHENTICATED | Missing, malformed, or expired access token. |
| 404 | NOT_FOUND | The user has no current_homes listing yet. |
| 409 | STATE_CONFLICT | The listing’s current status is not LIVE (e.g. it is DRAFT, HIDDEN, or DELETED). |
Example error — 409
Side effects
- Sets
current_homes.status = "HIDDEN"on the caller’s listing. updatedAtis bumped.- Hidden listings are filtered out of the match-candidate query (Phase 3 worker honours this flag).
- Enqueues a
match.recomputejob for the owner to drop stale match rows (Phase 3 worker; stub in Phase 2). - Existing matches and conversations are preserved.
See also
- Publish listing — the inverse transition.
- Get my current home
- Update my current home