The request

Add an endpoint that accepts a meal photo ID from the nutrition log and returns the actual image file or a retrievable URL.

Current behavior

When a client logs a meal and attaches a photo, the dailyNutrition/get response returns a mealPhoto object that contains only an id integer. There is currently no endpoint that accepts this ID and returns the image file or a direct URL. A /file/get or equivalent endpoint does not exist in the API reference.

What we're trying to build

We're building an AI-powered meal photo macro estimation workflow. Here's how the full flow works — and where it breaks:

Client logs a meal in Trainerize, attaches a photo, and includes #Meal in the description to trigger the workflow
Automation polls dailyNutrition/getList on a scheduled interval, filtering for entries where hasImage is true and the description contains the trigger keyword
A follow-up call to dailyNutrition/get retrieves the full meal detail including the mealPhoto.id
⚠ The photo ID cannot be resolved into an actual image — this is where the workflow breaks
The image would be passed to a vision AI model to estimate calories and macros
The macro estimate would be written back via dailyNutrition/addCustomFood and logged to the client's nutrition diary
A confirmation message is sent to the client via message/send
Every step in this workflow is supported by the existing API except step 4. The photo retrieval endpoint is the single missing piece.

Why this matters

AI vision models are now capable enough that meal photo analysis is a genuinely useful tool for coaches and clients. Trainerize already captures and stores these photos — the infrastructure is there. Exposing those files through the API would unlock a wide range of automation and AI-powered nutrition workflows that coaches are actively trying to build. This is the missing piece.

The ask

A /file/get or equivalent endpoint that accepts a meal photo ID from the nutrition log and returns the image file or a direct, retrievable URL.