Nutshell vs Salesflare

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.

Salesflare

The REST API has a public Swagger 2.0 file covering 71 operations, with typed filters on every list call and a 30-day trial that needs no card. No rate limit numbers, API changelog, SDK or audit log were found in the reviewed documentation, and API keys carry no documented scopes.

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

Salesflare

1. Send Authorization: Bearer <API key> to https://api.salesflare.com. A person creates the key in Settings, API keys
2. Set limit on every list call. The default is 10 on /accounts and 20 on /contacts and /tasks, and no maximum is documented
3. Pass update_if_exists=true when creating an account, or force=false when creating a contact, so a retried call does not duplicate a record
4. Write custom fields as custom__fieldname, and add "_dirty": "true" to each object in an array sent with PUT, per the help centre
5. Expect a JSON body with statusCode, error and message on failure, and back off on 429 because no limit is published