For Agents
Programmatically user login, okta sso authentication. Covers 86 operations with bearer authentication.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Tovuti LMS 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%2Ftovuti.io%2Ftovuti" | 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%2Ftovuti.io%2Ftovuti" | 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 Tovuti LMS API.
User login
Okta SSO authentication
Azure AD authentication
Refresh access token
GET STARTED
Use for: I need to user login, I want to okta sso authentication, Search for azure ad authentication, Find all refresh access token
Not supported: Does not handle payments, communications, or crm - use for education only.
Tovuti is a cloud-based Learning Management System (LMS) platform. This API provides programmatic access to manage users, courses, lessons, quizzes, events, teams, media, and more. The API exposes 86 endpoints secured with bearer authentication.
Create API token
Delete API token
List all API tokens
Patterns agents use Tovuti LMS API for, with concrete tasks.
★ Education Operations
Use the Tovuti LMS API to perform education operations programmatically. The API provides 86 endpoints covering core functionality including user login, okta sso authentication, azure ad authentication.
Call POST /login to user login
Automated Authentication Management
Automate authentication operations by combining multiple Tovuti LMS API endpoints. Agents can okta sso authentication and then azure ad authentication in a single workflow.
Call POST /oktaLogin to okta sso authentication, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Tovuti LMS 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 bearer tokens manually.
Search Jentic for 'user login', load the operation schema, and execute with Jentic-managed credentials
86 endpoints — tovuti is a cloud-based learning management system (lms) platform.
METHOD
PATH
DESCRIPTION
/login
User login
/oktaLogin
Okta SSO authentication
/azureLogin
Azure AD authentication
/refresh
Refresh access token
/token
Create API token
/token
Delete API token
/tokens
List all API tokens
/tokenData
Get token information
/login
User login
/oktaLogin
Okta SSO authentication
/azureLogin
Azure AD authentication
/refresh
Refresh access token
/token
Create API token
/token
Delete API token
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Tovuti LMS API by hand means obtaining and sending its bearer token, tracking the api.tovuti.io v1 host, and coding your own token refresh and request handling. Through Jentic you install once, import the Tovuti LMS API from the API Directory, store the token once, and your agent calls it.
Permission scoping
Tovuti's login and token operations carry their target in the request body rather than the URL path, so scope the agent to the operations it needs, such as logging in or listing tokens. You choose which operations are allowed, so ones like revoking a token are left out unless you add them.
Credential isolation
Your Tovuti bearer token 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 'log in a user' or 'list active tokens', and Jentic returns the matching Tovuti 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.
Stripe
Complementary API for broader integration workflows
Use alongside Tovuti LMS API for multi-service workflows
Specific to using Tovuti LMS API through Jentic.
What authentication does the Tovuti LMS API use?
The Tovuti LMS API uses a Bearer token in the Authorization header. 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 user login with the Tovuti LMS API?
Yes. Use the POST /login endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Tovuti LMS 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 user login through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'user login'. Jentic returns the matching Tovuti LMS API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Tovuti LMS API have?
The Tovuti LMS API exposes 86 endpoints covering authentication, users, courses operations.
Can I limit what my agent is allowed to do with the Tovuti LMS API?
Yes. Because Jentic One is self-hosted, you run the execution layer and your own rules decide which Tovuti operations and credentials the agent may use. Tovuti's login and token 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 logging a user in or listing tokens. Sensitive operations like revoking a token stay out of reach unless you explicitly allow them, and the stored bearer token is injected only for the calls you have approved.
/tokens
List all API tokens
/tokenData
Get token information