Freshsales API vs SugarAI (SugarCRM)

Freshsales API

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

SugarAI (SugarCRM)

The REST reference covers 350 endpoint pages with filters, field selection, bulk calls and upsert by sync_key. SugarAI's AI Supplemental Terms forbid connecting a customer's or third party's AI agent or MCP connector to the APIs unless Sugar has approved it, tokens carry no scopes, and no OpenAPI file, trial or SLA was found.

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

SugarAI (SugarCRM)

1. Confirm that Sugar has approved the agent integration before connecting. The AI Supplemental Terms forbid unapproved AI agents and MCP connectors on the APIs
2. POST to /rest/v11_27/oauth2/token with grant_type password and a platform other than base, mobile or portal, or the login can end the user's own session
3. Send the access token in the OAuth-Token header. It lasts 60 minutes by default, so store the refresh token and not the password
4. Stay under 20 requests a second on SugarCloud and reuse one session for batches. Over-limit traffic is blocked by IP address until support lifts it
5. Page with max_num and offset until next_offset is -1, and pass fields to keep responses small
6. Use PATCH /integrate/:module/:sync_key_field_name/:sync_key_field_value for writes that may be retried, since it inserts or updates by sync_key