Freshsales
Freshsales is the CRM application from Freshworks designed for sales teams, offering contact and account management, deal pipelines, AI-powered lead scoring, built-in phone and email, sales sequences, and CPQ. The Freshsales REST API enables CRUD access to contacts, accounts, deals, tasks, appointments, notes, and products for building integrations and sales workflow automation.
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 Freshsales 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 — Freshsales 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.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Freshsales
Each block below is one kind of artifact we hold for Freshsales. 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.
Freshsales CRM API
REST API for managing contacts, sales accounts, deals, tasks, appointments, notes, and CPQ products in Freshsales. Authentication uses a token-based scheme via the Authorization...
Freshsales Appointments API
The Appointments API from Freshsales — 2 operation(s) for appointments.
Freshsales Calls API
The Calls API from Freshsales — 1 operation(s) for calls.
Freshsales Contacts API
The Contacts API from Freshsales — 7 operation(s) for contacts.
Freshsales Deals API
The Deals API from Freshsales — 3 operation(s) for deals.
Freshsales Jobs API
The Jobs API from Freshsales — 1 operation(s) for jobs.
Freshsales Lists API
The Lists API from Freshsales — 2 operation(s) for lists.
Freshsales Notes API
The Notes API from Freshsales — 2 operation(s) for notes.
Freshsales Products API
The Products API from Freshsales — 2 operation(s) for products.
Freshsales SalesAccounts API
The SalesAccounts API from Freshsales — 3 operation(s) for salesaccounts.
Freshsales SalesActivities API
The SalesActivities API from Freshsales — 1 operation(s) for salesactivities.
Freshsales Search API
The Search API from Freshsales — 1 operation(s) for search.
Freshsales Tasks API
The Tasks API from Freshsales — 2 operation(s) for tasks.
Scroll within the panel for all 13 ·
Open Collections 1
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).
Freshsales CRM API
OPEN COLLECTIONGraphQL 1
Where a provider ships GraphQL, the schema is the contract. We profile it alongside the REST surface so the whole interface is legible in one place.
GraphQL schemas published by this provider.
Freshsales GraphQL Schema
This conceptual GraphQL schema represents the Freshsales CRM API domain model. Freshsales is the CRM application from Freshworks designed for sales teams, offering contact and a...
GRAPHQLSecurity 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 Freshsales — 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 1
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/freshsales · machine-readable index on apis.io