POST
Add listing photos

Overview

Attaches one or more previously-confirmed HOME_PHOTO uploads to the caller’s listing. The combined total (existing photos + the new batch) may not exceed 10. If the listing currently has no cover photo (i.e. this is the first batch attached outside the onboarding flow), the first photo in the batch is set as the cover. Each uploadId must already have been confirmed via POST /uploads/confirm and must belong to the caller — server cross-checks the uploads row by userId. This endpoint is reused after onboarding step 3 to add additional photos. During onboarding it is not used — step 3’s POST is the dedicated entry point.

Authentication

Bearer <accessToken> required. Scope: user.

Path parameters

None.

Query parameters

None.

Request body

photoMeta[] object

Example payload

Response — 200 OK

Returns the updated Home object including the appended photos.

Error responses

Example error — 400 (too many photos)

Side effects

  • Appends new entries to current_homes.photos[] with orderIndex continuing from the current last + 1.
  • If the listing has zero existing photos AND no cover, the first photo in the batch is set isCover: true.
  • updatedAt bumped.
  • When photoMeta is supplied, each photo’s blurhash, width, and height are stored from it; otherwise they default to ""/0/0.
  • Enqueues an image.process job per new photo (stub in Phase 2; Phase 7 generates thumbnails, EXIF strip, and can backfill a server-computed blurhash when the client did not supply one).

See also

curl