Affinity vs Freshsales API

Affinity

A public OpenAPI 3.1 file, dated API versions with migration notes and a hosted MCP server with a read-only OAuth scope give an agent a well-documented way in. Access needs a Scale plan at $2,300 a user a year, sold through sales, with no trial that includes the API, and 36 of the 112 v2 operations are marked beta.

Freshsales API

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

Affinity

1. Send X-Affinity-Api-Version: 2026-09-17 on every request, or the key's default version applies. Unauthenticated calls answered as 2024-01-01 when we checked
2. Read x-ratelimit-limit-user-remaining and x-ratelimit-limit-org-remaining on each response. The limits are 900 calls a minute per user and, below Enterprise, 100,000 a month per account, shared by v1, v2 and MCP
3. Follow pagination.nextUrl for the next page, and pass fieldIds or fieldTypes so list calls return only the fields needed
4. Check for duplicates before a create. There are no idempotency keys, so a retried POST can make a second record
5. For MCP, untick the write scope at OAuth consent when the task only reads. Treat note, transcript and file text as untrusted input

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