Food Recognition Kiosk Integration

Manage your Food Recognition Kiosk customers and link them to APIUsers so that intakes logged via Food Recognition Kiosk sync with your Food Recognition APP, Nutrition Management Platform, and Food AI Engine ecosystem.

Learn about account roles and tokens in User Types & Access Tokens.

Plan & Token Requirements

Feature available in the following LogMeal Plans:

Analyse

Monitor

Recommend

Custom

Accessible by the following User Types:

⚫ APICompany

What It Does

The Food Recognition Kiosk Integration exposes endpoints that let you register, list, and deactivate Kiosk customers and enumerate restaurants linked to your company. By linking Kiosk customers to 🔴 APIUser identities, all Kiosk-captured intakes become available across your LogMeal ecosystem (Food Recognition APP, Nutrition Management Platform, Food AI Engine).

When to Use It / Outcomes

You operate Food Recognition Kiosks and need to associate device intakes with your users.
You need to bulk import customer IDs for multiple restaurants.
You want to list Kiosk restaurants available to your company and manage customer mappings per restaurant.

Feature-Specific Details

Customer mappings use your external_user_id and the restaurant identifier (id_restaurant).
Bulk imports are supported via TSV with columns for IDs and restaurant mapping.
You can create, list, or deactivate customer identifiers globally for a restaurant or target a specific user by external_user_id.
Designed for organization-level use (⚫ APICompany token).

Related Endpoints

Use the following endpoints for Kiosk external integration:

POST /v2/kiosk/external/customers/import → ⚫ Bulk import Kiosk customer identifiers using a TSV file.
POST /v2/kiosk/external/customers → ⚫ Create Kiosk customer identifiers for a restaurant.
GET /v2/kiosk/external/customers → ⚫ List all customer identifiers grouped by restaurant.
DELETE /v2/kiosk/external/customers → ⚫ Deactivate all customers for a restaurant.
DELETE /v2/kiosk/external/customers/{external_user_id} → ⚫ Deactivate a specific customer by external ID.
GET /v2/kiosk/external/restaurants → ⚫ List restaurants available to your company.
GET /v2/kiosk/external/recipes → ⚫ List all company dish recipes with nutritional information and ingredients.
GET /v2/kiosk/external/recipe/{restaurant_class_id} → ⚫ Retrieve one dish recipe by its internal restaurant_class_id, including the same fields as in the list response. Use this for recipe details instead of loading every dish.
PATCH /v2/kiosk/external/recipe/{restaurant_class_id} → ⚫ Update a dish recipe.

Both recipe GET endpoints accept an optional language query parameter and return available_nutritional_sources. The list response contains company_recipes (array); the single-dish response contains recipe (object). Recipes are scoped to the requesting company; an unknown or inaccessible dish ID returns HTTP 404.