INTEGRATIONS

Integrate LogMeal into the products and workflows you already own

Use a RESTful API, structured JSON responses and role-based access tokens to connect LogMeal food intelligence with client-owned applications, professional workflows and operational systems.

integrations api
API

A RESTful API with structured responses

The LogMeal API is a RESTful service. Client applications send HTTP requests and receive structured JSON responses containing recognition, nutrition or intake-related data.

The current API base URL is https://api.logmeal.com/v2. The documentation provides endpoint-by-endpoint schemas, request examples and response structures.

IMPLEMENTATION

A practical path from first API call to production

1. Create the account and test user

Start with a trial account and obtain the appropriate token for the workflow.

2. Validate the core flow

Use the interactive documentation or code samples to recognize an image and inspect the response.

3. Add confirmation and data retrieval

Connect dish confirmation, ingredients and nutrition according to the product experience.

4. Add user and monitoring logic

Create users, managers, goals or history workflows when the product needs them.

5. Productionize the integration

Move tokens and business logic to the appropriate secure architecture and monitor limits, quotas and error handling.

Authentication

Role-based access for different product users

APICompany

Company-level account administration and user management.

APIUser

Represents an end user who submits meals, runs recognition and accesses their own nutrition-related data.

APIUserManager

Represents an authorized manager or professional who can access multiple users according to plan and permissions.

technology resources
Developer resources

Developer resources to accelerate integration

Quickstart

A guided first flow for recognition, ingredients and nutrition.

API Reference

Endpoint schemas, parameters, authentication requirements and examples.

Ready-to-use code

Code snippets in more than 35 programming languages.

Plans & Limits

Plan access, credits, daily limits and per-second limits.

Integration patterns

Choose the integration model that matches the product

Client-owned application

Use the Food AI Engine directly inside a mobile, web or digital-health product.

Professional monitoring

Combine API users and manager access with the Nutrition Management Platform.

Ready-to-use mobile front end

Use the Food Recognition APP when you need an end-user interface without building it from scratch.

Facility integration

Use tray recognition or kiosk workflows when recognition must operate inside a physical service environment.

Integration questions

What format does the API return?

Requests use bearer tokens. The token type depends on whether the caller is a company administrator, end user or authorized manager.

Requests use bearer tokens. The token type depends on whether the caller is a company administrator, end user or authorized manager.

Yes. The interactive documentation can be used to validate tokens and payloads before moving to code.

Yes. LogMeal provides ready-to-use code examples in more than 35 programming languages.

Ready to integrate food intelligence into your product?

Start with the documentation or discuss your architecture and use case with our technical team.
Talk to technical sales

This site is registered on wpml.org as a development site. Switch to a production site key to remove this banner.