Freshsales

REST API at {domain}.myfreshworks.com/crm/sales/api/. Contacts: standard CRUD at /contacts with custom fields. Accounts: /sales_accounts for company records. Deals: /deals with pipeline stages and value. Activities: /tasks, /appointments, and /notes. Search: /search endpoint with query string and entity type filter. Bulk operations for contact, account, and deal CRUD. The API follows standard REST patterns with JSON payloads. Custom fields are accessible via api_name identifiers. Activities link to contacts and deals via association. The API supports views (filtered lists) that mirror the UI. Pagination uses page/per_page parameters. Webhook support for entity changes. The API design is functional but some endpoint patterns are inconsistent (different URL structures for different entities).

API errors return JSON with errors object containing field-specific messages. Standard HTTP status codes. Rate limits: per-plan — free accounts get lower limits. The limits page documents exact thresholds per plan. Bulk operation errors return per-record error details. Search API can be slow on large datasets — agents should use specific filters. Custom field validation errors return the field name and constraint violation. Webhook delivery is reliable with retry on failure. The main reliability consideration: Freshsales is part of a larger platform, and platform-wide incidents can affect CRM API availability. For agents, rate limit monitoring and bulk operation error handling are the main operational concerns.

Freshsales (part of Freshworks CRM) provides sales CRM with AI-powered lead scoring, built-in communication channels, and tight integration with the Freshworks ecosystem (Freshdesk, Freshchat, etc.). For agents, the API covers contacts, accounts (companies), deals, tasks, appointments, notes, and sales activities. Freddy AI provides lead and deal scoring — predictive intelligence on which leads are most likely to convert. Workflows automate repetitive sales processes. The Freshworks platform advantage: agents using both Freshdesk and Freshsales can link customer support data with sales data. The API is adequate for standard CRM operations but less developer-focused than Close or HubSpot. For agents building sales workflows within the Freshworks ecosystem, Freshsales is a natural fit.

API token authentication via Authorization: Token token={api_key} header. Tokens are per-user, generated in profile settings. The token inherits the user's role and permissions. No fine-grained token scoping. OAuth 2.0 is available for marketplace app integrations. Token doesn't expire by default. For agents, creating a dedicated API user with appropriate permissions provides access control. The Freshworks platform uses a unified authentication model — one account can access Freshsales, Freshdesk, and other products. No IP-based restrictions. The auth model is simple but the Token header format is non-standard (Token token=... instead of Bearer). For agents already in the Freshworks ecosystem, the unified auth simplifies multi-product integration.

Developer documentation at developers.freshworks.com/crm covers API reference, authentication, webhooks, and marketplace development. The API reference documents endpoints with parameters and response examples. The documentation is organized by entity type (contacts, deals, accounts, activities). SDKs are limited — no official REST API client libraries (only marketplace app SDKs). Code examples use cURL. The Freshworks Developer Portal provides tools for marketplace app development. Documentation quality is adequate but less polished than HubSpot or Close. The ecosystem documentation helps agents understand cross-product integration patterns. For agents, the contacts and deals API reference plus the authentication guide are the key starting points.