Upload photos to a location

Attaches one or more images to a location. Supply a photos array where each item carries at least photo, a public image URL that Listings API fetches and stores. locationId and a non-empty photos array are always required.

Two shapes of success

A small batch uploads inline: photos carries the finished media and request is an empty object, as in the sample above. A large batch is queued instead, and the same 200 looks like this:

{  "data": {    "addLocationPhotos": {      "clientMutationId": null,      "success": true,      "request": {        "requestId": "e6c2d9d9-9a18-4015-88cf-9a4e19a6f49a",        "status": "PROCCESSING"      },      "photos": [],      "errors": null    }  }}

Both are successes, so handle them by testing whether request.requestId is present rather than by assuming photos is populated.

The URL field is photo. Not url, and not image. Alongside it each item accepts an optional type (LOGO, COVER, or ADDITIONAL), starred, and source; publisherOverride and partnerMediaId are also accepted for partner integrations. A returned photo has no caption field.

Use case: seed a new location's imagery. Right after creating a location such as "Jenny Home", POST its logo and storefront photos by URL in a single call. The response returns each new photo's id, which you pass to the star and remove endpoints later.

Use case: reuse an approved asset across locations. Point multiple locations at the same hosted image URL in their photos arrays so every location shares the same source asset.

Gotchas.

• Images must be JPEG or PNG. Publisher size rules apply per category (a typical floor is ~10 KB and ceiling of a few MB).
• Large batches are processed asynchronously. Above a server-side batch size, the call queues the work instead of uploading inline: photos comes back empty and request.requestId is set. Poll GET /locations/photos/requests/{requestId} with that id to track completion. The threshold is server-side configuration, so treat it as "large batches may be queued" rather than a fixed number, and branch on whether request.requestId is present.
• Do not switch on request.status. On the queued response it is the literal string PROCCESSING, which is spelled differently from the PROCESSING the poll endpoint reports for the same job. request.requestId being present is the reliable signal.
• Passing starred: true on more than the 4 allowed starred photos fails the whole call with SY15012. The check counts the location's existing starred photos plus the starred items in this request.
• A location keeps a single logo and single cover; re-uploading either category replaces the existing image.
• Set type explicitly when you mean an image to be the logo or cover. Without it the image is stored as an additional photo.