---
title: "Guest Business Photo"
method: GET
path: "/v1/guest/business/photo.jpg"
tags: ["guest"]
---

# Guest Business Photo

`GET /v1/guest/business/photo.jpg`

The storefront for a guest's row — the twin of `geo/photo.jpg`.

IT SHIPS WITH `guest_business_suggest` OR NOT AT ALL. The rows that route
answers with carry a Places photo resource name, and a photo-less row draws
a magnifier where a shop front goes — so serving the rows publicly and
keeping the pictures behind a workspace would have replaced a 2.3 second
wait with a list of grey rows that visibly re-lay-out when the mint lands.
The owner's note on this list is that the picture is the point ("add images
preview they must recognize it").

THE KEY STAYS HERE, exactly as it does on the team route: a Places photo is
a resource NAME behind a keyed endpoint, and the bytes are fetched by us.
What a caller can do with this is ask Google for a photograph of a business
on Google Maps, which is a thing they can already do.

## Query parameters

- `name` string
- `width` integer

## Headers

- `authorization` string, nullable
- `x-darwin-token` string, nullable

## Response `200`

Successful Response

- unknown

## Other responses

- `422` — Validation Error

## Changes

> 33 revisions in range; 1 not diffed.

- **2026-09-26** `faea4a09e09c` — 2 info
  - added the new optional `header` request parameter `authorization`
  - added the new optional `header` request parameter `x-darwin-token`
- **2026-09-04** `cb4b3e1a2e37` — 1 info
  - endpoint added

[Change history](https://skmtc.dev/stormy/apis/stormy-control-plane/changes/v1/guest/business/photo.jpg/get.md)

---

[API](https://skmtc.dev/stormy/apis/stormy-control-plane.md) · [All operations](https://skmtc.dev/stormy/apis/stormy-control-plane/llms.txt) · [OpenAPI document](https://skmtc.dev/stormy/apis/stormy-control-plane/revisions/52151384d62a?raw)