For Agents
Programmatically updates current user's data., get user info. Covers 623 operations.
Use for: I need to updates current user's data., I want to user info, Search for user, Find all user
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
Tolgee Platform REST API reference. The API exposes 623 endpoints.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Tolgee API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ftolgee.io%2Ftolgee" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ftolgee.io%2Ftolgee" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with Tolgee API.
Updates current user's data.
Get user info
Update user
Delete user
Enable TOTP
GET STARTED
Disable TOTP
Patterns agents use Tolgee API for, with concrete tasks.
★ Developer Tools Operations
Use the Tolgee API to perform developer tools operations programmatically. The API provides 623 endpoints covering core functionality including updates current user's data., get user info, update user.
Call POST /v2/user to updates current user's data.
Automated Localization keys Management
Automate localization keys operations by combining multiple Tolgee API endpoints. Agents can get user info and then update user in a single workflow.
Call GET /v2/user to get user info, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Tolgee API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle none tokens manually.
Search Jentic for 'updates current user's data.', load the operation schema, and execute with Jentic-managed credentials
623 endpoints — tolgee platform rest api reference.
METHOD
PATH
DESCRIPTION
/v2/user
Updates current user's data.
/v2/user
Get user info
/v2/user
Update user
/v2/user
Delete user
/v2/user/password
Update password
/v2/user/mfa/totp
Enable TOTP
/v2/user/mfa/totp
Disable TOTP
/v2/user/mfa/recovery
Regenerate Codes
/v2/user
Updates current user's data.
/v2/user
Get user info
/v2/user
Update user
/v2/user
Delete user
/v2/user/password
Update password
/v2/user/mfa/totp
Enable TOTP
/v2/user/mfa/totp
Disable TOTP
/v2/user/mfa/recovery
Regenerate Codes
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Tolgee by hand means pointing at the app.tolgee.io host, tracking its v2 user and localization routes, and coding your own request and pagination handling. Through Jentic you install once, import the Tolgee API from the API Directory, store the credential once, and your agent calls it.
Permission scoping
Tolgee's user operations carry their target in the request body rather than the URL path, so scope the agent to the operations it needs, such as reading the current user's data. You choose which operations are allowed, so account changes like deleting the user or resetting MFA are left out unless you add them.
Credential isolation
Your Tolgee credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'get the current user' or 'update user data', and Jentic returns the matching Tolgee operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Github
Alternative developer tools API
Choose Github when you need a different approach to developer tools operations
Specific to using Tolgee API through Jentic.
What authentication does the Tolgee API use?
The Tolgee API uses no authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I updates current user's data. with the Tolgee API?
Yes. Use the POST /v2/user endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Tolgee API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I updates current user's data. through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'updates current user's data.'. Jentic returns the matching Tolgee API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Tolgee API have?
The Tolgee API exposes 623 endpoints covering localization keys, translation labels, tolgee llm proxy API operations.
Can I limit what my agent is allowed to do with the Tolgee API?
Yes. Because Jentic One is self-hosted, your own rules decide which Tolgee operations and credentials the agent can use. Tolgee's user operations carry their target in the request body rather than the URL path, so you scope the agent to just the operations it needs, such as reading the current user's data with GET /v2/user. Account changes like deleting the user with DELETE /v2/user or resetting MFA on /v2/user/mfa are left out unless you explicitly allow them.