Get a menu item's photo
The photo a restaurant published of one menu item. The same lookup the MCP item_photo tool runs. A photo Layout already holds answers at once and draws no allowance. Otherwise Layout reads the restaurant's own site, answering 200 when the photo turns up within about 12 seconds and 202 finding with an imageId when it does not; poll GET /images/items/{imageId}. Layout stops looking 35 seconds after the request. Read-only: nothing is built or charged to the person.
Request
- Base URL: https://api.layout.link/v1
- URL: https://api.layout.link/v1/images/items
- Auth: HTTP bearer
Headers
The API version you code against. Optional; without it you get 2026-10-01, the current version. Layout answers with the version it used.
Optional. Any 1 to 255 visible ASCII characters, unique per real intent. A retry with the same key and the same body gets the stored response for 24 hours, with Idempotent-Replayed: true, and is never run twice. The same key with a different body is 409 idempotency_conflict; while the first request is still running it is 409 in_progress with Retry-After. Only a success is stored: any error releases the key so it can be sent again. A 4xx ran nothing. A 5xx may have run, above all a confirm's 500, so read the resource before sending anything changed.
Request body
Example request
{
"item": "box combo",
"placeId": "ChIJbloomCoffee",
"query": "Raising Cane's",
"near": "Roseville, CA"
}Response
An answer: the photo, or why there is none.
Example response
{
"image": {
"url": "https://cdn.layout.link/items/d/raisingcanes.com/the-box-combo-0e9d083ec191.jpg"
}
}Changes
No recorded changes to this operation across all 1 revision of this API.