Know of an official OpenAPI document? Contribute it →
For Agents
Programmatically balance, statistics. Covers 54 operations with apiKey authentication.
Use for: I need to balance, I want to statistics, Search for transfer, Find all search
Not supported: Does not handle payments, crm, or developer tools - use for communications only.
The world's greatest SMS API. The API exposes 54 endpoints secured with apiKey authentication.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the www.zoomconnect.com, 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%2Fzoomconnect.com%2Fzoomconnect" | 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%2Fzoomconnect.com%2Fzoomconnect" | 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 www.zoomconnect.com API.
balance
statistics
transfer
search
create
update
getUser
Patterns agents use www.zoomconnect.com API for, with concrete tasks.
★ Communications Operations
Use the www.zoomconnect.com to perform communications operations programmatically. The API provides 54 endpoints covering core functionality including balance, statistics, transfer.
Call GET /api/rest/v1/account/balance to balance
Automated account Management
Automate account operations by combining multiple www.zoomconnect.com endpoints. Agents can statistics and then transfer in a single workflow.
Call GET /api/rest/v1/account/statistics to statistics, then verify the result
AI Agent Integration via Jentic
AI agents discover and call www.zoomconnect.com 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 apiKey tokens manually.
Search Jentic for 'balance', load the operation schema, and execute with Jentic-managed credentials
54 endpoints — the world's greatest sms api.
METHOD
PATH
DESCRIPTION
/api/rest/v1/account/balance
balance
/api/rest/v1/account/statistics
statistics
/api/rest/v1/account/transfer
transfer
/api/rest/v1/account/user
search
/api/rest/v1/account/user
create
/api/rest/v1/account/user/{userId}
update
/api/rest/v1/account/user/{userId}
getUser
/api/rest/v1/contacts/all
all
/api/rest/v1/account/balance
balance
/api/rest/v1/account/statistics
statistics
/api/rest/v1/account/transfer
transfer
/api/rest/v1/account/user
search
/api/rest/v1/account/user
create
/api/rest/v1/account/user/{userId}
update
/api/rest/v1/account/user/{userId}
getUser
/api/rest/v1/contacts/all
all
What agents get from Jentic-routed access to this vendor.
Setup
Wiring ZoomConnect by hand means passing its email and token API-key headers on every request to the www.zoomconnect.com/app host and handling failures yourself. Through Jentic you install once, import ZoomConnect from the API Directory, store the credential once, and your agent calls it.
Permission scoping
ZoomConnect puts the user id in the URL path (/api/rest/v1/account/user/{userId}), so a rule can pin your agent to one user: it can read that user and nothing else. You choose the operations it may call, so ones like transferring account balance or updating a user are not included unless you add them.
Credential isolation
Your ZoomConnect email and token 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 'check account balance' or 'list all contacts', and Jentic returns the matching ZoomConnect 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.
Specific to using www.zoomconnect.com API through Jentic.
What authentication does the www.zoomconnect.com use?
The www.zoomconnect.com uses an API key passed in the `email` 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 balance with the www.zoomconnect.com?
Yes. Use the GET /api/rest/v1/account/balance endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the www.zoomconnect.com?
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 balance through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'balance'. Jentic returns the matching www.zoomconnect.com operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the www.zoomconnect.com have?
The www.zoomconnect.com exposes 54 endpoints covering account, contacts, groups operations.
Can I limit what my agent is allowed to do with the ZoomConnect API?
Yes. Because you self-host Jentic One, your own rules decide which ZoomConnect operations and credentials the agent may use. Since ZoomConnect puts the user id in the URL path, such as /api/rest/v1/account/user/{userId}, you can pin the agent to a single user so it only reads that user and nothing else. You pick the operations it may call, so sensitive ones like transferring account balance or updating a user are excluded unless you explicitly add them.
GET STARTED