Cliengo Connect API

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

★ Only Publicly Available OpenAPI DocumentCRMContact Managementbearer11 EndpointsREST

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.

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.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 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 API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Cliengo Connect API, keeping it validated and agent-ready.

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.

Use Cases

Patterns agents use Cliengo Connect API 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 the Jentic vault. 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

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Cliengo Bearer tokens are stored encrypted in the Jentic vault. Agents receive scoped tokens and never see the raw Authorization value.

Intent-based discovery

Agents search Jentic with intents like 'list chatbot contacts' or 'send a whatsapp template message' and Jentic returns the matching Cliengo Connect operations with their input schemas.

Time to first call

Direct Cliengo Connect integration: 1-2 days for auth, contact polling, and WhatsApp template handling. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

ClickSend

ClickSend can dispatch SMS or email follow-ups instead of using Cliengo's WhatsApp endpoint.

Choose ClickSend when the agent needs to follow up via SMS or email rather than WhatsApp templates.

Complementary

Clientary

Clientary handles invoicing once a Cliengo lead converts into a paying client.

Pair when a Cliengo lead converts and the agent needs to issue an invoice or estimate.

Complementary

Clicksign

Clicksign collects e-signatures on agreements with leads captured by Cliengo.

Pair when an agent needs to escalate a Cliengo-qualified lead into a signed agreement.

FAQs

Specific to using Cliengo Connect API 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 at https://app.jentic.com/sign-up.

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.