Install Jentic One Beta

Connect the Cliengo Connect API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Cliengo Connect 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%2Fcliengo.com%2Fcliengo" | sh

Step 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%2Fcliengo.com%2Fcliengo" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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.

Capabilities

What an agent can do with Cliengo Connect API.

Pull leads captured by Cliengo chatbots through GET /contacts and sync them into a downstream CRM

Read full conversation transcripts via GET /conversations/{conversationId} for handoff or quality review

Send a templated WhatsApp message to a contact via POST /whatsapp/messages

List approved WhatsApp templates with GET /whatsapp/templates before sending

GET STARTED

Start building with Cliengo Connect API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Cliengo Connect API for, with concrete tasks.

★ Lead Capture Sync

Sales operations teams sync leads captured by Cliengo chatbots into Salesforce or HubSpot. The agent polls GET /contacts on a schedule, transforms the payload, and writes into the destination CRM. End-to-end sync setup is a few hours rather than building a Cliengo-to-CRM connector from scratch.

List contacts created in the last 24 hours and return name, email, and originating website for each

WhatsApp Re-engagement

Marketing teams re-engage cold leads via WhatsApp templates. The agent lists templates with GET /whatsapp/templates, picks an approved follow-up, and sends to the contact's WhatsApp number through POST /whatsapp/messages. Template-based sending stays inside Meta's compliance window for outbound messaging.

Send the 'follow_up_v2' WhatsApp template to contact +5491155555555 and confirm the message was queued

Conversation Transcript Audit

Quality-assurance teams pull conversation transcripts via GET /conversations/{conversationId} and grade chatbot responses against a rubric. The agent fetches transcripts in batches, runs them through a scoring prompt, and reports issues back to the bot owner.

Fetch the last 50 conversations and return the conversation IDs of any that contain the phrase 'speak to a human'

Agent-Driven Lead Workflow

An AI agent embedded in a sales tool ingests new Cliengo leads, qualifies them with an LLM, sends a WhatsApp follow-up to qualified leads, and writes the rest to a nurture list. Through Jentic, the agent searches for 'list chatbot contacts', loads the operation, and executes against credentials in your Jentic One instance. Total setup time is under an hour.

List today's contacts, identify ones with a phone number containing country code +54, and send the qualified template to each

Key Endpoints

11 endpoints — jentic publishes the only available openapi specification for cliengo connect api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/contacts

List leads captured by chatbots

POST

/contacts

Create a contact record

GET

/conversations/{conversationId}

Get a conversation transcript

GET

/whatsapp/templates

List approved WhatsApp templates

POST

/whatsapp/messages

Send a templated WhatsApp message

GET

/agents

List human agents on the account

GET

/contacts

List leads captured by chatbots

POST

/contacts

Create a contact record

GET

/conversations/{conversationId}

Get a conversation transcript

GET

/whatsapp/templates

List approved WhatsApp templates

POST

/whatsapp/messages

Send a templated WhatsApp message

GET

/agents

List human agents on the account

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Cliengo Connect API by hand means managing its bearer token against connect.cliengo.com/v1 and mapping calls across contacts, conversations, WhatsApp templates, and messages yourself. Through Jentic you install once, import the Cliengo Connect API from the API Directory, store the token once, and your agent calls it.

Permission scoping

Cliengo takes contact and message details in the request body, so scope the agent to the operations it needs, such as listing contacts and sending a WhatsApp template message. You choose which operations are in the allowed set, so contact creation is not callable unless you add it.

Credential isolation

Your Cliengo 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 'list chatbot contacts' or 'send a WhatsApp template message', and Jentic returns the matching Cliengo Connect operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Cliengo Connect API through Jentic.

Why is there no official OpenAPI spec for Cliengo Connect API?

Cliengo does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Cliengo Connect API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Cliengo Connect API use?

The Cliengo Connect API uses Bearer token authentication. The token is generated in the Connect API settings inside the Cliengo dashboard and sent in the Authorization header. Through Jentic, the token is stored encrypted in the vault and injected at execution time so agents never see the raw value.

Can I send a WhatsApp message to a contact with the Cliengo Connect API?

Yes. POST /whatsapp/messages dispatches a templated WhatsApp message. List approved templates first via GET /whatsapp/templates so the agent only references templates that are eligible for outbound sending.

What are the rate limits for the Cliengo Connect API?

Rate limits are not declared in the OpenAPI spec. Cliengo applies plan-tier limits visible in your account settings - confirm them before high-volume contact polling. Through Jentic, throttle responses surface as standard error objects an agent can retry against.

How do I pull chatbot leads from Cliengo through Jentic?

Run pip install jentic, then search Jentic for 'list chatbot contacts' to find GET /contacts. Load the operation schema, supply pagination parameters, and execute. Jentic injects the Bearer token from the vault and returns a structured contact list ready for downstream CRM writes.

Can I retrieve the full transcript of a chatbot conversation?

Yes. GET /conversations/{conversationId} returns the conversation including the messages exchanged, useful for quality review and human handoff. Listing endpoints exist at GET /conversations for paginated retrieval.

Can I limit what my agent is allowed to do with the Cliengo Connect API?

Yes. Because you run Jentic One yourself, your own rules decide which Cliengo Connect operations and credentials the agent may use. You can allow only the operations the task needs, such as listing contacts with GET /contacts and sending a template with POST /whatsapp/messages, while leaving contact creation, updates, and deletes out of the allowed set so the agent cannot call them. The bearer token stays under your control and is injected at execution time, so the agent acts only within the scope you define.

Cliengo Connect API

Name: Cliengo Connect API
Brand: Cliengo Connect API
Availability: InStock

Agent-ready OpenAPI document · curated by JenticCRMContact Managementbearer11 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Pull leads and conversation transcripts from Cliengo chatbots, manage contact records, and send templated WhatsApp messages so agents can act on chatbot-captured leads.

Use for: I need to retrieve all leads captured by my Cliengo chatbot today, Get the conversation transcript for a specific lead, Send a WhatsApp follow-up to a contact captured by the chatbot, List the WhatsApp templates approved on my Cliengo account

Not supported: Does not handle live chatbot configuration, conversation flow editing, or chatbot training - use for reading chatbot-captured contacts and conversations and sending WhatsApp templates only.

Jentic publishes the only available OpenAPI specification for Cliengo Connect API, keeping it validated and agent-ready. Cliengo is a Latin American AI-powered chatbot platform focused on website lead capture and conversational engagement, and the Connect API exposes the contacts and conversations its bots produce. The 11-endpoint surface covers contact CRUD, read access to conversation transcripts, WhatsApp template listing and outbound WhatsApp message sending, plus inventory endpoints for the websites and agents configured on the account.

Jentic One on Github View OpenAPI Document

Connect the Cliengo Connect API to your agent

Capabilities

Start building with Cliengo Connect API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Cliengo Connect API