---
updatedAt: 2026-11-02T02:02:24.000Z
agentTools:
projectIndex: https://docs.logmeal.com/llms.txt
---
# User Types & Access Tokens
> Understanding how users and tokens work is essential for integrating with the Food AI Engine API and the **Nutrition Management Platform**.\
> Tokens determine **who** is making the request and **what resources** they can access β both for direct API calls and when using the Nutrition Management Platform.
***
## User Types
There are three types of users in the LogMeal ecosystem. Each has different responsibilities and access scopes:
| Icon | User Type | Usage |
| ------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| β« **APICompany** | Account-level manager. Created automatically when you sign up to the API. | Responsible for creating and managing APIUsers and APIUserManagers. Only one per subscription. |
| π΄ **APIUser** | Represents an end-user of your app or service. Each final user must have their own APIUser. A user-specific **language** and **country** can be assigned during creation. APIUsers can later update these attributes via `/modifyUserProfileInfo` endpoints or directly in the [Food Recognition APP](./guides-features-app-white-label). These fields are essential for **localized nutrition analysis**, ensuring that recognition, nutritional values, and recommendations align with the userβs regional context. | They can log meals, submit intakes, run food recognition, and track nutritional history. Their data also powers dashboards inside the Nutrition Management Platform. |
| π΅ **APIUserManager** | Supervisor users (e.g. healthcare professionals, nutritionists). Their access is available only in higher-tier plans (e.g. Monitor or higher). | They can view and manage the intakes of multiple APIUsers. Managers often work directly inside the Nutrition Management Platform to visualize and manage usersβ nutrition data. |
π For a quick overview, see the [Plans & Limits](./guides-essential-concepts-plans-limits) page for which user types are supported under each plan.
***
## Access Tokens
Each user has a unique **access token** β a non-transferable secret key used to authenticate API calls.
* **APICompany Token** (β«): Issued when you subscribe to the API. Found in the βProfileβ section of the dashboard. Used to create/manage APIUsers and APIUserManagers.
* **APIUser Token** (π΄): Issued automatically when creating an APIUser. Required for recognition endpoints (e.g. image analysis, intake submission). These users also have access to the white-labeled [Food Recognition APP](./guides-features-app-white-label). They can also update their profile information with dedicated endpoints.
* **APIUserManager Token** (π΅): Issued automatically when creating an APIUserManager. Grants access to dashboards and endpoints for managing user intakes and goals. APIUserManagers use this token both in the API and when signing in to the Nutrition Management Platform.
> **Best Practice:** Always keep tokens secret. Treat them like passwords. Do not expose them in client-side code.
**Token lifetime and rotation:** WEB sessions expire seven days after issuance, regardless of activity. Authorized users can replace all existing API/WEB tokens for an account using `POST /v2/users/tokens/rotate` with an API bearer and a password proof from `/v2/users/tokens/reauth` (valid for 10 minutes). The web portal also supports WEB sessions. An API bearer alone cannot rotate itself. Rotation immediately invalidates the old tokens, without issuing new token types.
***
## Creating Users
You can create users either through the LogMeal Users Dashboard, or via the User Management API:
### 1. Web Dashboard
* Log in with your company account at LogMeal Login Page
* Go to the LogMeal Users Dashboard.
* Choose whether to add a new APIUser or APIUserManager.
* Fill in details (language, username, email, password if required).
* After creation, the system assigns an **ID** and a **Token**.
π For an overview of how nutrition professionals can use these accounts, visit Nutrition Management Platform.
***
### 2. User Management API Endpoints
If you prefer automation, you can use the **APICompany token (β«)** to call user management endpoints:
* **Create APIUser** β [**POST /users/signUp**](https://docs.logmeal.com/reference/post_v2-users-signup#/)
* **Create APIUserManager** β [**POST /managers**](https://docs.logmeal.com/reference/post_v2-managers#/)
* **Assign access** (link APIUserManager β APIUser) β [**POST /managers/userAccess**](https://docs.logmeal.com/reference/post_v2-managers-useraccess#/)
* **Modify APIUser profile** β [**POST /users/modifyUserProfileInfo**](https://docs.logmeal.com/reference/post_v2-managers-modifyuserprofileinfo-userid#/). This endpoint allows updating country and language attributes, among others.
* `country` ensures nutritional values and datasets are adapted to local standards.
* `language` personalizes the userβs experience in the Food Recognition APP and Platform as well as in the name of dishes, ingredients and nutritional indicators.
* **Enable / disable APIUser accounts** β [**POST /users/toggleEnabled/\{userId}**](https://docs.logmeal.com/reference/post_v2-users-toggleenabled-userid#/).
Use this endpoint to **temporarily revoke or restore access** for an existing π΄ **APIUser** without deleting the account:
* When a user is **disabled**, they can no longer log in to Food Recognition APPs/Nutrition Platform or use their credentials to access the APIs.
* When re-enabled, the same user can resume usage with their existing configuration and access.
* An APIUser can check its current status through [**GET /profile/getUserProfileInfo**](https://docs.logmeal.com/reference/get_v2-profile-getuserprofileinfo#/), which returns the `enabled` boolean. APICompanies can also inspect this value through **GET /users/APIUsers**.
π See the [External Management feature](https://docs.logmeal.com/docs/guides-features-external-management#/) for more details on how to manage APIUserManager users.
***
## Example Workflows
1. **App End-User (π΄ APIUser)**
* A mobile app creates an APIUser for each registered user.
* That token is then used for calls like [**POST /image/segmentation/complete**](https://docs.logmeal.com/reference/post_v2-image-segmentation-complete#/) or [**GET /intake/\{imageId}**](https://docs.logmeal.com/reference/get_v2-intake-imageid#/).
* The same user can log in to the white-labeled [Food Recognition APP](./guides-features-app-white-label) to view their intake history and nutrition insights. They can also update **profile preferences** such as `language` and `country`, which directly influence how nutritional information and recommendations are presented.
2. **Nutrition Management Platform (π΅ APIUserManager)**
* A clinic creates APIUserManagers for dietitians or healthcare professionals.
* Each manager can view the intake history of multiple clients or patients (π΄ APIUsers).
* Managers typically use the Nutrition Management Platform as their dashboard to analyze patient data, set goals, and monitor adherence.
3. **Company-Level Control (β« APICompany)**
* An admin uses the APICompany token to onboard new users and assign supervisors.
* They also manage organizational settings in the LogMeal Dashboard.
***
## Next Steps
* [Image Pre-processing](./guides-essential-concepts-image-pre-processing) β how to prepare images before recognition.
* [Plans & Limits](./guides-essential-concepts-plans-limits) β which users and endpoints are included in each plan.
* [API Documentation](https://docs.logmeal.com/reference/https://docs.logmeal.com/reference/getting-started#/) β exact endpoints and request/response schemas.
* Learn how professionals use the Nutrition Management Platform in real-world nutrition workflows.