Freshsales API vs Nutshell

Freshsales API

Contact upsert and bulk upsert of up to 100 records make creates safe to retry. No MCP server for Freshsales.

Nutshell

The REST reference is served as Markdown with an OpenAPI fragment per operation, and the hosted MCP server uses OAuth with PKCE and can only read. No rate limit numbers, error format or API changelog were found in the reviewed documentation, and API keys carry no scopes.

Freshsales API

1. Build the base URL from the bundle alias shown under the API key, https://<alias>.myfreshworks.com/crm/sales/api/
2. Use /api/contacts/upsert rather than create, so a retry updates instead of duplicating
3. Budget calls, since 1,000 an hour covers the whole account and 429s carry no Retry-After
4. Add include=owner,sales_accounts to pull related records in one call
5. Expect to see only what the key owner's role can see

Nutshell

1. Authenticate REST calls with HTTP Basic, a Nutshell user's email as username and the API key as password, against https://app.nutshell.com/rest
2. Use IDs in the <number>-<type> form, such as 3-accounts, and send updates as JSON Patch with content-type: application/json-patch+json
3. Page lists with page[limit] and page[page], which is 0-based, and call /accounts/list/fields or the lead and contact equivalents for valid filter keys
4. Use the REST API for writes. The MCP server only reads, and OAuth tokens need the read scope
5. Filter webhook events yourself, because every webhook receives all events and subscriptions are created in Setup, not through the API