Guest Business Photo
Changed onThe 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.
Request
- Base URL: https://api.stormy.ai (the document declares no server; this is the origin it was published from)
- URL: https://api.stormy.ai/v1/guest/business/photo.jpg
- Auth: none declared
Query parameters
Headers
Response
Successful Response
Changes
- info
added the new optional
headerrequest parameterauthorization - info
added the new optional
headerrequest parameterx-darwin-token
- info
- info
endpoint added
- info