For Agents
Programmatically login-user, create-user. Covers 55 operations with basic, bearer authentication.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the WhatsApp Business 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%2Fwhatsapp.local%2Fwhatsapp-local" | 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%2Fwhatsapp.local%2Fwhatsapp-local" | 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 WhatsApp Business API.
Login-User
Create-User
Get-User
Update-User
GET STARTED
Use for: I need to login-user, I want to create-user, Search for get-user, Find all update-user
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
See https://developers.facebook.com/docs/whatsapp. The API exposes 55 endpoints secured with basic, bearer authentication.
Delete-User
Logout-User
Get-Application-Settings
Patterns agents use WhatsApp Business API for, with concrete tasks.
★ Developer Tools Operations
Use the WhatsApp Business API to perform developer tools operations programmatically. The API provides 55 endpoints covering core functionality including login-user, create-user, get-user.
Call POST /users/login to login-user
Automated Users Management
Automate users operations by combining multiple WhatsApp Business API endpoints. Agents can create-user and then get-user in a single workflow.
Call POST /users to create-user, then verify the result
AI Agent Integration via Jentic
AI agents discover and call WhatsApp Business 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 basic, bearer tokens manually.
Search Jentic for 'login-user', load the operation schema, and execute with Jentic-managed credentials
55 endpoints — see https://developers.
METHOD
PATH
DESCRIPTION
/users/login
Login-User
/users
Create-User
/users/{UserUsername}
Get-User
/users/{UserUsername}
Update-User
/users/{UserUsername}
Delete-User
/users/logout
Logout-User
/settings/application
Get-Application-Settings
/settings/application
Update-Application-Settings
/users/login
Login-User
/users
Create-User
/users/{UserUsername}
Get-User
/users/{UserUsername}
Update-User
/users/{UserUsername}
Delete-User
/users/logout
Logout-User
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the WhatsApp Business API by hand means choosing between its basic auth and bearer token per call and handling retries yourself across its user and settings surface. Through Jentic you install once, import the WhatsApp Business API from the API Directory, store the credentials once, and your agent calls it.
Permission scoping
The WhatsApp Business API puts the username in the URL path (/users/{UserUsername}), so a rule can pin your agent to reading one user: it can fetch that user and nothing else. You choose the operations it may call, so destructive ones like updating or deleting a user are not included unless you add them.
Credential isolation
Your WhatsApp Business API basic and bearer credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'log in a user' or 'read application settings', and Jentic returns the matching WhatsApp Business API 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 WhatsApp Business API through Jentic.
What authentication does the WhatsApp Business API use?
The WhatsApp Business API uses basic, bearer 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 login-user with the WhatsApp Business API?
Yes. Use the POST /users/login endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the WhatsApp Business 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 login-user through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'login-user'. Jentic returns the matching WhatsApp Business API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the WhatsApp Business API have?
The WhatsApp Business API exposes 55 endpoints covering users, application, backup/restore operations.
Can I limit what my agent is allowed to do with the WhatsApp Business API?
Yes. Because you self-host Jentic One, your own rules decide which WhatsApp Business API operations and credentials the agent may use. Since the username lives in the URL path (/users/{UserUsername}), you can pin the agent to reading a single user with GET /users/{UserUsername} and nothing else. You choose the operations it may call, so destructive ones like PUT or DELETE /users/{UserUsername} are excluded unless you add them.
/settings/application
Get-Application-Settings
/settings/application
Update-Application-Settings