Klenty API Documentation

This is the complete API documentation for connecting to the Klenty API using MindCloud's Universal API. If you are new to MindCloud, start with the Introduction to see how one API can sit in front of many different apps.

MindCloud is an integration company that offers one normalized API to access 3,100+ apps from a single place. It cleans up provider-specific quirks, keeps requests and responses consistent, and centralizes authentication so you do not need to manage separate flows for every app. Browse other apps.

Meet Klenty: Manage prospects, lists, cadences, and sales outreach. Keep reading to get started.

Quickstart

Before you run your first Klenty request, you need three things:

1. A MindCloud account — sign in or create an account at MindCloud.
2. A MindCloud API Key — create one in API Keys. Keep it on your server.
3. At least one Klenty connection — create or choose one in Connections. Note its connectionId.

Every Klenty action uses the same URL pattern:

https://connect.mindcloud.co/v1/universal/klenty/latest/actions/{actionSlug}

You need a MindCloud API Key and a Klenty connection. Then call an action such as Get Call Completion Details:

curl --request GET \
  --url "https://connect.mindcloud.co/v1/universal/klenty/latest/actions/get-call-completion-details" \
  --header "Authorization: Bearer $MINDCLOUD_API_KEY" \
  --get \
  --data-urlencode "connectionId=$CONNECTION_ID"

Every response comes back in the same envelope, with your rows in a data array:

{
  "success": true,
  "data": [
    { "id": "1042", "name": "Ava" }
  ],
  "meta": {}
}

After your first request works, use Shape your requests to control arguments, pagination, filtering, fields, and errors.

Authentication

Authentication has two layers. Your MindCloud API Key authenticates the request to MindCloud, sent as a Bearer token in the Authorization header. The connectionId selects the connected Klenty account that should run the action. MindCloud stores and refreshes the Klenty credentials behind that connection, so you never send provider tokens with your requests.

Pass connectionId in the query string for GET and DELETE actions, and in the JSON body for POST, PUT, and PATCH actions. Keep your MindCloud API Key on your server; do not ship it in browser code, mobile apps, public repositories, or logs.

Klenty actions

All 31 published actions for this Klenty version. Each page documents the endpoint, arguments, and response controls.

• PUTAdd Prospect Custom Field Value
• PUTAdd Prospect To List
• PUTAdd Tags To Prospect
• POSTAdd Webhook
• POSTBulk Create Prospects
• PUTChange Prospect To Do Not Contact
• POSTCreate Prospect
• DELETEDelete Webhook
• GETGet Call Completion Details
• GETGet Email Engagements
• GETGet Prospect By Email
• GETGet Prospect Status By Email
• GETGet Prospect Status By ID
• GETGet Prospect With Custom Fields
• GETGet Stepwise Metric Engagements
• GETList Company Cadences
• GETList Lists
• GETList Prospects By Created Date
• GETList Prospects By Last Updated Date
• GETList Prospects By List
• GETList User Cadences
• GETList Webhooks
• PUTRemove Tags From Prospect
• PUTResume Cadence
• PUTRevert Prospect From Do Not Contact
• POSTStart Cadence
• PUTStop Cadence For Prospect
• PUTStop Prospect Mails
• PUTUnsubscribe Prospect
• PUTUpdate Prospect
• PUTUpdate Webhook

Related apps

More Sales & CRM apps on the Universal API, behind the same REST shape. Or browse all apps.

HubSpotPipedriveGoogle TasksGoogle ContactsTodoistZoho CRMFollow Up BossClose