Plans & Limits

The LogMeal API offers several subscription plans. Each plan unlocks different sets of features, subject to quotas and request limits.
This guide explains how plans work, which limits apply, and how to check your usage programmatically.

Subscription Plans

🆓

Free (Trial) Tier

When you first sign up, you get a 30-day Free trial with unlimited access to all endpoints across all plans. This allows you to explore every feature before committing to a paid plan. After 30 days, you’ll need to choose a subscription plan (Analyse, Monitor, Recommend, Custom) to continue.

LogMeal features are divided into four subscription tiers:

• 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.

⚠️

All higher-tier plans include the features of lower-tier plans.
For up-to-date pricing, see the LogMeal Pricing Page.

ℹ️ See the complete list of available LogMeal API features and their plan-level access in the Features Overview.

Plan Access at a Glance

⏱ Request Limits and Quotas

All plans are subject to quotas and request limitations.

ℹ️

Contact us if you want to upgrade your plan limitations.

• © Monthly credits

  • Shared across all 🔴 APIUsers.
  • Calls beyond the monthly limit consume extra credits.

• (D) Daily request limits

  • Each user can send a limited number of requests per day.
  • Example: 20 image recognitions/day per 🔴 APIUser on standard plans.

ℹ️

If you reach the daily request limit during your initial integration phase you might want to create more APIUsers for testing purposes. Learn more about how to create and manage User Types & Access Tokens.

• (S) Per-second request limits

  • Restricts how many requests can be made in real time.
  • Example: 1 image/second per 🔴 APIUser on standard plans.

• Other per-endpoint limits (⏱)
  Some endpoints include custom restrictions noted directly in their docs.

⚠️

If you exceed these limits, the API will return HTTP 429 Too Many Requests. Even on the 🆓 Free (Trial) tier, requests are subject to the same daily (D) and per-second (S) limits as standard plans. However, no extra monthly usage will be allowed during the trial.

How to Check Your Limits

You can check your current quotas and limits programmatically with the Informative Endpoints:

• GET /v2/info/limitations → Returns account-level quotas and current usage.

This allows you to dynamically enforce limits in your own application logic.

Usage & Limits via Response Headers (Credit-Consuming Endpoints)

For any endpoint call that consumes credits (for example, image recognition endpoints), LogMeal returns usage headers in the HTTP response.
These headers let you track both end-user daily request limits and company billing-period credits without calling an extra endpoint.

End-User (APIUser token) — Daily Requests (Rolling 24h)

The following headers are returned when the request has a daily request limit associated:

• RateLimit-Limit: Maximum requests allowed for the APIUser token within a rolling 24-hour window.

• RateLimit-Remaining: Requests still available for the APIUser token right now (post-call) within the rolling 24-hour window.

• RateLimit-Reset: Number of seconds until the next request slot becomes available (i.e., when the oldest request in the last 24 hours expires). If RateLimit-Remaining is 0, retry after RateLimit-Reset seconds.

Company (APICompany billing period) — Credits

The following headers are returned on credit-consuming requests:

• X-Account-Credits-Used: Total credits consumed by the company since the start of the current billing period (since the last billing date).

• X-Account-Credits-Remaining: Credits remaining for the company until the next billing date.

How to read these headers

cURL example (shows response headers):

curl -i -X POST "https://api.logmeal.com/..." \
  -H "Authorization: Bearer <token>" \
  -F "image=@./food.jpg"

Combining Plans and User Types

Plan access works in combination with user type tokens:

• ⚫ APICompany – company-wide admin, creates and manages users.
• 🔴 APIUser – end-users of your app (one per person).
• 🔵 APIUserManager – managers/clinicians with access to multiple APIUsers.

An endpoint may require both a minimum plan level and a specific user type.
For example: Custom Occasions requires Monitor or higher AND ⚫/🔵 token access.

Next Steps:

• After your 30-day 🆓 Free (Trial) ends, choose a subscription plan on the LogMeal Pricing Page to keep using the API.
• Learn about how to create and manage User Types & Access Tokens
• Explore Food Recognition Capabilities