Welcome to the LogMeal API Reference. This section provides a factual, endpoint-by-endpoint description of the LogMeal API, based directly on our OpenAPI specification.

An API is a simple way for your app to talk to LogMeal over the internet—your app sends a request (e.g., an image), and the API returns structured results in json format (e.g., recognized foods and nutrition).

If you’re new to LogMeal, we recommend starting with the Quickstart section. Once you’ve completed your first successful request, come back here to explore every endpoint in detail.

Base URL

All API requests are made to the following base URL:

https://api.logmeal.com/v2

Authentication

The LogMeal API uses Bearer Tokens for authentication. Each request must include an Authorization header with the correct token type:

Authorization: Bearer YOUR_TOKEN

⚫ APICompany token – used for company-level management (creating APIUsers, assigning plans, etc.)
🔴 APIUser token – used by end-users of your app for logging meals and fetching nutritional info
🔵 APIUserManager token – used by managers/clinicians to access multiple users’ histories

👉 For more details, see User Types & Access Tokens.

Rate Limits & Quotas

Some endpoints are limited by:

Monthly credits (© icon)
Daily request limits ((D) icon)
Per‑second request limits ((S) icon)

The endpoints that have some type of limitation are indicated with the icon ⏱. You’ll find the relevant limits listed in each endpoint description. For a complete overview, see Plans & Limits.

Plan Subscription Limits

Depending on your subscription plan, you may have access to different sets of endpoints:

Analyse: Essential food recognition, ingredients, and nutritional extraction.
Monitor: Extended monitoring features: history, goals, custom occasions, and more.
Recommend: Advanced AI features: Nutri-Scores, recommendations, food quantity detection, food waste detection.
Custom: Enterprise or custom integrations tailored to your needs.

If you are using our free time-limited trial plan you will have temporary access to ALL endpoints.

👉 See the full Plans & Limits guide for detailed access by feature.

Error Handling

The API returns standard HTTP status codes:

200 OK – Request succeeded
400 Bad Request – Invalid input
401 Unauthorized – Missing or invalid token
403 Forbidden – Token does not have access rights
404 Not Found – Resource does not exist
429 Too Many Requests – Rate limit exceeded
500 Internal Server Error – Something went wrong on our end

For troubleshooting tips, see Guides > Essential Concepts > Best Practices > Troubleshooting.

Next Steps

Explore the full list of API Endpoints
Review available Features