© Consumes your monthly credits. Limited amount of monthly calls, exceeding calls will be charged as extras.

(D) Limited amount of daily calls per user.

(S) Limited amount of calls per second.

It applies the same food segmentation procedure as in /image/segmentation/complete and additionally it automatically calculates the food quantity for each of the detected regions. The only output difference in this endpoint is that an additional attribute named 'serving_size' is provided for each of the elements inside the 'segmentation_results' list.

Geographic Personalization: we recommend setting the country parameter associated to the end-user (APIUser) before applying any food recognition/segmentation call. See any /modifyUserProfileInfo endpoint for additional details.

Additionally, any endpoint and internal procedure that is based on food quantity uses by default the automatically estimated food quantity (e.g. ingredients definition or nutritional information estimation). Note that the segmentation_results might not be directly applicable to the uploaded image size. The segmentation pixel values are scaled depending on the 'processed_image_size' values provided for each of the images (the images might be sometimes resized depending on the needs of the food recognition algorithms used).

In order to compute the food quantity a depth image has to be provided. The depth image must be extracted using the LogMeal Depth SDK, that you will have to integrate into your App accordingly. Two SDKs are available, the iOS Depth SDK and the Android Depth SDK.

IMPORTANT: Note that this endpoint has two parameters in the request body ('image' and 'depth') which are in the 'multipart/form-data', and the remaining parameters are in 'application/json'. You can check it from the dropdown from the right corner.