Be the first to get access to new connectors. Get early access →
ConnectorBay Early access

CleverTap (BYOK) — connector documentation

  • MCP endpoint: https://byok-clevertap.connectorbay.com/mcp
  • REST API: POST https://byok-clevertap.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-clevertap.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own CleverTap account passcode, sent in the X-Upstream-Key header and the CleverTap account (project) ID in X-Upstream-Key-2 of every request (never stored, logged or cached)
  • Health: https://byok-clevertap.connectorbay.com/health · Tool schemas: https://byok-clevertap.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-clevertap · agent@connectorbay.com

What CleverTap (BYOK) is for

CleverTap (BYOK) lets an AI assistant read your own CleverTap data through the CleverTap API with a key you supply (account passcode). Read-only: 9 tools (list_api_campaigns, get_campaign_report, get_event_count, get_profile_count, get_event_trend, get_top_event_property_values, get_live_active_users, list_catalogs, list_content_blocks). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to in1.api.clevertap.com, sg1.api.clevertap.com, us1.api.clevertap.com, aps3.api.clevertap.com, mec1.api.clevertap.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by CleverTap. CleverTap and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "Which API campaigns did CleverTap schedule in September 2026?"
  • "How many messages did CleverTap campaign 1457432766 send and how many were clicked?"
  • "How many Charged events happened in CleverTap last month?"
  • "How many users did a Charged event in CleverTap in September?"
  • "Show the daily number of Charged events in CleverTap for September 2026"
  • "What are the most common Amount values on Charged events in CleverTap?"

What it does

  • list_api_campaigns: List campaigns created through the CleverTap API whose scheduled start falls in a date range, with id, name, schedule time and status.
  • get_campaign_report: Get the report of one finished campaign by its numeric id (see list_api_campaigns): messages sent and clicked.
  • get_event_count: Count how many times an event happened in a date range. The status can be partial while the result is still being computed; ask again shortly.
  • get_profile_count: Count the user profiles that performed an event in a date range. The status can be partial while the result is still being computed; ask again shortly.
  • get_event_trend: Get an event's counts per day, ISO week or month over a range of up to one year, as event totals or distinct users. The status can be partial while the result is still being computed; ask again shortly.
  • get_top_event_property_values: Get the most (or least) frequent values of one event property over a date range, with their counts. The status can be partial while the result is still being computed; ask again shortly.
  • get_live_active_users: Get the number of users active in the last five minutes, optionally split by new vs returning, session source, browser, OS and device.
  • list_catalogs: List product catalogs with name, description, product count, status and creation time, 100 per page at most.
  • list_content_blocks: List content blocks (reusable message snippets) with id, name, type, author and dates. The snippet text itself is not returned.

BYOK key

You bring your own CleverTap account passcode (https://developer.clevertap.com/docs/authentication). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to in1.api.clevertap.com, sg1.api.clevertap.com, us1.api.clevertap.com, aps3.api.clevertap.com, mec1.api.clevertap.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

Live from the CleverTap API (in1.api.clevertap.com, sg1.api.clevertap.com, us1.api.clevertap.com, aps3.api.clevertap.com, mec1.api.clevertap.com) with a BYOK key; documentation: https://developer.clevertap.com/docs/getting-started. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by CleverTap. CleverTap and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your CleverTap account.

Built for: Worldwide. Languages: English.