Freshsales API review

What an hour of requests buys

Freshsales meters requests, not records, so the work an hour can do depends entirely on how many records each request carries. These are the shapes the reference documents.

Bulk upsert is the call that changes the arithmetic. It exists for contacts, accounts and deals, takes up to 100 entities a request keyed on a unique identifier such as an email, and runs as a background job you can track through the Job Status API. An account may have 10 bulk upserts in progress at once.

The search and lookup endpoints are the other place an integration spends its hour. A sync that looks each record up by email before writing it spends two requests a record and halves its throughput, where an upsert keyed on email does the match and the write in one.

Freshsales API pricing, plan by plan

Freshsales API pricing is seat pricing: the API comes with every plan, and the published ceiling of 1,000 requests an hour does not change between them.

Freshworks advertises saving 20% on annual billing, and the monthly prices sit behind a toggle on the pricing page. Two add-ons are available on every plan: branded documents at $19 a user a month, and the Freddy AI Agent at $49 per 100 sessions, with 500 sessions included once per account.

The trial is 21 days of the full CRM, after which you pay by card to continue or the account is suspended. There is no ongoing free tier on the published plans.

One number, per hour, per account

Freshsales API rate limits are a single figure, stated in the reference where it explains a 429: 1,000 API requests per hour per account. There is no per-endpoint accounting and no daily pool to plan around, only the hour.

So the Freshsales API rate limits are simple to state and strict to live with. A design built on 100-record upserts and paged reads of saved views fits comfortably, and a design built on single-record reads does not fit at all once the account has more than a few thousand contacts.

How to create a Freshsales API key

A Freshsales API key belongs to a user and is found in the app under Profile Settings, API Settings. The same tab shows the bundle alias, which identifies the CRM account and becomes part of every URL.

Because the key carries its owner's access, the integration should run on a dedicated user with the scope it needs and no more. That also keeps a departing employee from taking a working sync with them.

A first Freshsales API call

Both calls below are Freshsales' own examples from the reference: a single contact read, and a bulk upsert keyed on email that creates or updates in one request.

# read one contact
GET https://{yourdomain}.myfreshworks.com/crm/sales/api/contacts/1
Authorization: Token token=$FRESHSALES_API_KEY

# create or update up to 100 in one request
POST /api/contacts/bulk_upsert
# returns a job_status_url to poll

Where the Freshsales API documentation lives

The Freshsales API documentation is one long reference page, organized by object, with the authentication rules, error codes and pagination at the top and a curl example under every endpoint.

Lists are paginated at 25 records a page by default, with a page parameter starting at 1. The reference also covers configuration selectors for owners, territories, deal stages and currencies, which a sync reads once at startup to map IDs to names, and custom modules for accounts on Enterprise.

Freshsales' own product walkthrough

Freshsales publishes this on its own channel, so it is Freshsales' account of Freshsales, not ours. It is here because a rate card cannot show you the thing moving, and a few minutes of the product is faster than any paragraph on this page at telling you whether the shape of it fits yours.

Freshworks' own three minute overview of Freshsales: lead capture, qualification and routing with Freddy AI, and the sales workspace. It does not cover the API, and nothing in it touches the 1,000 requests an hour that decides what a Freshsales integration can do, so the limits section above is the part to read.

Published 10 June 2024 on Freshworks, the channel Freshsales' own pages link to, and read on 23 October 2026. Nothing in it is a source for a price or a limit on this page: every figure in the tables above comes from a Freshsales page.

Strengths and limits

Freshsales is one of the two cheapest seats here with a stated API ceiling, and the API is honest about how small that ceiling is.

The two columns are the same fact seen from either side. A cheap seat with a small, fixed ceiling suits a team whose integration batches its writes, and punishes one that reads record by record.

Who should actually buy this

Buy Freshsales when the seat price matters and the integration can batch. At $9 a user it ties for the cheapest paid CRM seat here at list price, and a sync built on 100-record upserts fits inside 1,000 requests an hour with room to spare.

Do not buy it for throughput. The ceiling is per account and does not grow with plans or seats, so a fifty-person team on Enterprise has the same hourly budget as three people on Growth. If several integrations will share the account, count their requests together before signing.

Against Zoho CRM, the other cheap seat that publishes its whole API allowance, the difference is in what grows. Zoho's daily credit pool rises with licenses and edition, and it publishes per-call costs and a free edition. Freshsales publishes one fixed hourly number and a cheaper seat. A growing team that integrates heavily is better served by Zoho; a small team with a light, batched sync can save the difference on Freshsales.

Before you build against it

Three things to settle first, each one read off Freshsales' own pages. The ticks are remembered in this browser, so you can come back to a half-finished integration.

If Freshsales is not the answer

Four providers in the CRM and sync APIs listing that solve the same problem differently. Each one is a trade, and the trade is named.

The full set, organized by the reason people leave, is on the Freshsales alternatives page.

Freshsales against the obvious rival

Same rate cards, read side by side, with the arithmetic done on a worked volume rather than left to you: HubSpot vs Freshsales, Freshsales vs Zoho CRM, Freshsales vs Salesforce and Freshsales vs Pipedrive.

Every pairing in the directory is on the compare hub.