Freshchat
Freshchat is Freshworks' modern messaging and customer engagement platform that enables sales and support teams to converse with customers across web, mobile, WhatsApp, Facebook Messenger, Instagram, Apple Business Chat, and email. The Freshchat REST API provides programmatic access to agents, users, conversations, messages, channels, bots, and reports for building custom integrations and workflow automations. Authentication uses Bearer API tokens generated from the Freshchat admin console.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Freshchat the way a machine reads it — 20 machine-readable artifacts across 13 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Freshchat scores 32.4/100 (thin), with a separate agent-readiness read of 41/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
How we profile Freshchat
Each block below is one kind of artifact we hold for Freshchat. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 13
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Freshchat Accounts API
The Accounts API from Freshchat — 1 operation(s) for accounts.
Freshchat Agents API
The Agents API from Freshchat — 3 operation(s) for agents.
Freshchat BusinessHours API
The BusinessHours API from Freshchat — 1 operation(s) for businesshours.
Freshchat Channels API
The Channels API from Freshchat — 1 operation(s) for channels.
Freshchat Conversations API
The Conversations API from Freshchat — 3 operation(s) for conversations.
Freshchat CSAT API
The CSAT API from Freshchat — 1 operation(s) for csat.
Freshchat Files API
The Files API from Freshchat — 2 operation(s) for files.
Freshchat Groups API
The Groups API from Freshchat — 1 operation(s) for groups.
Freshchat Messages API
The Messages API from Freshchat — 1 operation(s) for messages.
Freshchat Metrics API
The Metrics API from Freshchat — 2 operation(s) for metrics.
Freshchat OutboundMessages API
The OutboundMessages API from Freshchat — 2 operation(s) for outboundmessages.
Freshchat Roles API
The Roles API from Freshchat — 1 operation(s) for roles.
Freshchat Users API
The Users API from Freshchat — 4 operation(s) for users.
Scroll within the panel for all 13 ·
Open Collections 2
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Freshchat Webhooks
OPEN COLLECTIONFreshchat REST API
OPEN COLLECTIONSecurity Posture 4
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Freshchat — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 1
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/freshchat · machine-readable index on apis.io