POST
Onboarding step 3 — photos

Overview

Attaches the user’s confirmed HOME_PHOTO uploads to the listing created in step 2, and designates which one is the cover photo. This endpoint is a one-shot during onboarding — the listing is created with photos: [] and step 3 appends them in a single call. After step 3 has fired, further photo edits go through the post-onboarding photo endpoints (POST /current-home/me/photos, PATCH /current-home/me/photos/reorder, etc.). Re-submitting step 3 returns 409 STATE_CONFLICT. currentStep stays at 3 until both photos AND description are submitted — only then does it advance to 4. Preconditions:
  • currentStep is exactly 3.
  • A step-2 listing exists with photos.length === 0.
  • Every photoUploadId references a confirmed upload owned by the caller with fileType: 'HOME_PHOTO'.
  • coverPhotoId is one of photoUploadIds.
  • Total photo count would not exceed 10.

Authentication

Bearer <accessToken> required. Scope: user.

Path parameters

None.

Query parameters

None.

Request body

photoMeta[] object

Example payload

Response — 200 OK

Returns the refreshed onboarding state (same shape as GET /onboarding/state). currentStep stays 3 until the description is also submitted.

Example response

Error responses

Example error — 400

Side effects

  • Appends each photo as an embedded subdocument on the user’s current_homes document (url, thumbnailUrl, orderIndex, isCover, fileSizeBytes). When photoMeta is supplied, blurhash, width, and height are stored from it; otherwise they default to ""/0/0.
  • Exactly one photo is marked isCover: true — the entry whose id matches coverPhotoId.
  • Does NOT advance currentStep on its own — only the description PATCH does that.

See also

curl