ChatKitty Platform API

Name: ChatKitty Platform API API
Brand: ChatKitty Platform API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCommunicationsChat MessagingapiKey, oauth267 EndpointsREST

For Agents

Manage chat channels, send and moderate messages, control user sessions, and run analytics on a hosted chat platform across 67 endpoints.

Connect the ChatKitty Platform API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the ChatKitty Platform 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 ChatKitty Platform API API.

Create, list, and delete chat channels and manage channel members and moderators

Send channel messages, direct messages, and typing keystroke events in real time

Import existing channels, members, and message history from another chat backend in batch

Run server-side chat functions to react to message events and customize moderation logic

GET STARTED

Start building with ChatKitty Platform API API

Explore with Jentic

View OpenAPI Document

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

Jentic publishes the only available OpenAPI specification for ChatKitty Platform API, keeping it validated and agent-ready. ChatKitty is a chat infrastructure platform that powers in-app messaging with channels, direct messages, threads, and presence. The API exposes 67 endpoints covering channel and message management, user and session control, chat functions for server-side message handling, bulk imports, and analytics exports. It is designed for product teams adding real-time chat to mobile, web, and gaming apps without operating their own messaging backend.

Use Cases

Patterns agents use ChatKitty Platform API API for, with concrete tasks.

★ In-App Customer Support Chat

Add real-time customer support chat to a SaaS product so users can message agents from inside the app. The ChatKitty API creates a channel per support thread, sends messages with POST /v1/channels/{id}/messages, and uses chat functions to route incoming messages to on-call agents. Pagination over /v1/channels/{id}/messages keeps history manageable, and analytics endpoints surface response times and message volumes.

Create a channel named 'support-ticket-4521', add the customer and the agent as members, and send an initial system message confirming the ticket was opened.

Community Channels for a Mobile App

Power public and private community channels in a social or gaming app where users join topic-based rooms and exchange messages. The API handles channel creation, membership lists, moderator assignment, and reported-message review. Existing communities can be migrated through the bulk import endpoints under /v1/imports/channels and /v1/imports/messages, so launch is not blocked by historical data.

List all reported messages in channel id 'general' and delete any that match a banned-word list.

Chat Engagement Analytics

Track how active users are inside a chat product by exporting message and user analytics on a schedule. The /v1/analytics/messages and /v1/analytics/users endpoints kick off export jobs whose status can be monitored via /v1/jobs/{id}. Output feeds product dashboards for daily active chatters, channel popularity, and moderator coverage, replacing manual log scraping.

Trigger a message analytics export for the last 30 days and poll job status until it completes.

AI Agent Moderation and Concierge

Use an AI agent through Jentic to monitor channels, summarise long threads, and respond to keyword triggers in real time. The agent calls Jentic's search to find ChatKitty operations, loads schemas for sending messages or fetching channel history, and executes calls without touching raw OAuth client credentials. This turns a hosted chat product into an agent-aware surface for customer concierge or community moderation tasks.

Search Jentic for 'send a chat message', load the ChatKitty send-message schema, and post a welcome message to every newly created channel in the last hour.

Key Endpoints

67 endpoints — jentic publishes the only available openapi specification for chatkitty platform api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/v1/channels

Create a chat channel

POST

/v1/channels/{id}/messages

Send a message to a channel

GET

/v1/channels/{id}/messages

List messages in a channel

POST

/v1/channels/{id}/members

Add a member to a channel

POST

/v1/imports/messages

Bulk import historical messages

POST

/v1/analytics/messages

Export message analytics

GET

/v1/chat-sessions

List active chat sessions

POST

/v1/channels

Create a chat channel

POST

/v1/channels/{id}/messages

Send a message to a channel

GET

/v1/channels/{id}/messages

List messages in a channel

POST

/v1/channels/{id}/members

Add a member to a channel

POST

/v1/imports/messages

Bulk import historical messages

Why though Jentic?

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

Credential isolation

ChatKitty OAuth 2.0 client credentials and X-Token values are stored encrypted in the Jentic vault. Agents receive scoped, short-lived access tokens — raw client secrets never enter the agent's context.

Intent-based discovery

Agents search by intent (e.g., 'send a chat message' or 'create a channel') and Jentic returns the matching ChatKitty operation with its input schema, so the agent can call the right endpoint without browsing the docs site.

Time to first call

Direct ChatKitty integration: 1-3 days for OAuth setup, channel modelling, and moderation hooks. Through Jentic: under 1 hour to send a first message and list channel history.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Sendbird Chat API

Sendbird is a larger hosted chat platform with broader SDK coverage and enterprise compliance certifications.

Choose Sendbird when the customer needs HIPAA or SOC 2 attestations and rich mobile SDKs out of the box; choose ChatKitty for a leaner API surface and chat-functions-style server hooks.

Alternative

PubNub API

PubNub is a real-time messaging and presence network usable as a lower-level chat substrate.

Pick PubNub when the agent needs raw pub/sub channels and presence with custom data models; pick ChatKitty when it needs ready-made channels, members, and moderation primitives.

Complementary

Twilio API

Twilio handles SMS, voice, and email so out-of-app notifications can supplement in-app chat.

Use Twilio alongside ChatKitty to text or call users when they are offline and missed an in-app message.

FAQs

Specific to using ChatKitty Platform API API through Jentic.

Why is there no official OpenAPI spec for ChatKitty Platform API?

ChatKitty does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call ChatKitty Platform 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 ChatKitty Platform API use?

The API supports two schemes. Most operations use OAuth 2.0 client credentials against https://authorization.chatkitty.com/oauth/token with scopes such as create:*, read:*, update:*, and delete:*. A few endpoints accept an X-Token header for password-reset flows. Through Jentic, OAuth client credentials are stored in the encrypted vault and the agent only ever sees scoped tokens.

Can I send a message to a channel with the ChatKitty Platform API?

Yes. Call POST /v1/channels/{id}/messages with the channel id and message body. The same path also lists prior messages via GET, so an agent can fetch context before posting. Keystroke and channel-event endpoints under the same channel resource handle typing indicators and custom events.

What are the rate limits for the ChatKitty Platform API?

The OpenAPI spec does not declare numeric rate limits. ChatKitty enforces per-application throttling that varies by plan, so production agents should handle 429 responses with exponential backoff and surface the Retry-After header to the caller.

How do I import existing chat history into ChatKitty through Jentic?

Use Jentic to search for 'import chat messages', load the schema for POST /v1/imports/messages, and execute with a JSON batch of historical messages. Pair with /v1/imports/channels and /v1/imports/users to migrate the surrounding channel and member structure in the same run.

Can I run custom moderation logic with chat functions?

Yes. POST /v1/functions/{id}/versions creates a new version of a chat function, and GET /v1/functions/{id}/invocations lists past runs. Functions execute server-side on message events, so moderation, profanity filtering, and routing logic stay close to the chat backend rather than running in the client.