OVERALL CONTROL / 0.6-customer-control
Grades and scoring
Data access
25% of the overall score before applicability adjustment.
Scored answers and evidence
Read interface 7.5/10
Structured API for the declared product scope
Nutshell current REST contacts/accounts APIs and webhooks using customer Basic credentials; Enterprise read-only SQL is disclosed as a separate route.
REST supports retrieving standard CRM entities.
Nutshell API route overview ↗
REST API · Checked 2026-10-16
Bulk delivery 2.5/10
Manual report download
Nutshell current REST contacts/accounts APIs and webhooks using customer Basic credentials; Enterprise read-only SQL is disclosed as a separate route.
Saved Nutshell lists export CSV; REST collection pagination was not verified here.
Nutshell current REST availability ↗
Other integration points · Checked 2026-10-16
Query expressiveness 8.8/10
Documented structured API filters
Nutshell current REST contacts/accounts APIs and webhooks using customer Basic credentials; Enterprise read-only SQL is disclosed as a separate route.
Current REST route supports lists, filters and reports.
Nutshell API route overview ↗
REST API · Checked 2026-10-16
Access cost barrier 10.0/10
Access is free, or included in the lowest paid plan with no fixed access fee; published usage-only charges are eligible
Nutshell current REST contacts/accounts APIs and webhooks using customer Basic credentials; Enterprise read-only SQL is disclosed as a separate route.
Full API access has no additional charge for all customers; SQL is separate Enterprise scope.
Nutshell current REST availability ↗
Quick answer; all plans FAQ · Checked 2026-10-16
Third-party accessibility
20% of the overall score before applicability adjustment.
Scored answers and evidence
Third-party eligibility 10.0/10
Customer authorization without discretionary provider approval
Nutshell current REST contacts/accounts APIs and webhooks using customer Basic credentials; Enterprise read-only SQL is disclosed as a separate route.
Customers build integrations and connect business systems through the open REST API.
Nutshell current REST availability ↗
Why use a CRM API; getting started · Checked 2026-10-16
Downstream permission -
-
Nutshell current REST contacts/accounts APIs and webhooks using customer Basic credentials; Enterprise read-only SQL is disclosed as a separate route.
The reviewed technical documentation does not establish contractual permission for the declared downstream processing.
Nutshell API route overview ↗
Reviewed product documentation; stated limitation not resolved · Checked 2026-10-16
External action
15% of the overall score before applicability adjustment.
Scored answers and evidence
Write interface 7.5/10
Create and update in one business domain
Nutshell current REST contacts/accounts APIs and webhooks using customer Basic credentials; Enterprise read-only SQL is disclosed as a separate route.
POST creates a contact and PATCH edits contact audience membership.
Nutshell contact creation and audience membership changes ↗
Creating a person; Updating audience membership · Checked 2026-10-16
Custom application path 10.0/10
Customer applications using fixed APIs without provider selection
Nutshell current REST contacts/accounts APIs and webhooks using customer Basic credentials; Enterprise read-only SQL is disclosed as a separate route.
Customer API keys support custom apps and integrations.
Nutshell API authentication ↗
API authentication · Checked 2026-10-16
Continuity
15% of the overall score before applicability adjustment.
Scored answers and evidence
Refresh mechanism 7.5/10
Documented updated-since filters or webhooks
Nutshell current REST contacts/accounts APIs and webhooks using customer Basic credentials; Enterprise read-only SQL is disclosed as a separate route.
Webhooks notify selected CRM record changes.
Nutshell webhooks ↗
Qualifying events · Checked 2026-10-16
Limit visibility -
-
Nutshell current REST contacts/accounts APIs and webhooks using customer Basic credentials; Enterprise read-only SQL is disclosed as a separate route.
A numeric quota and recovery contract are not established by the reviewed route documentation.
Nutshell API route overview ↗
Reviewed product documentation; stated limitation not resolved · Checked 2026-10-16
CDC and deletion capture 5.0/10
Updates identified; deletion capture not established
Nutshell current REST contacts/accounts APIs and webhooks using customer Basic credentials; Enterprise read-only SQL is disclosed as a separate route.
Webhook documentation establishes updates, but not exhaustive deletion identity coverage.
Nutshell webhooks ↗
Qualifying events; partial-list warning · Checked 2026-10-16
Replay and gap recovery 2.5/10
Rebuild from a fresh snapshot; no historical replay established
Nutshell current REST contacts/accounts APIs and webhooks using customer Basic credentials; Enterprise read-only SQL is disclosed as a separate route.
Repeat a saved-list export to rebuild its current selected records; no historical/deleted payload recovery established.
Nutshell current REST availability ↗
Other integration points · Checked 2026-10-16
Data exit
20% of the overall score before applicability adjustment.
Scored answers and evidence
Export custody 7.5/10
Customer-held structured files or API records
Nutshell current REST contacts/accounts APIs and webhooks using customer Basic credentials; Enterprise read-only SQL is disclosed as a separate route.
Saved lists download in CSV for external use.
Nutshell current REST availability ↗
Other integration points · Checked 2026-10-16
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
Nutshell current REST contacts/accounts APIs and webhooks using customer Basic credentials; Enterprise read-only SQL is disclosed as a separate route.
No retrieval window or export charge at cancellation is established by these technical sources.
Nutshell API route overview ↗
Reviewed product documentation; stated limitation not resolved · Checked 2026-10-16
Planned migration fidelity 7.5/10
Portable structured records on documented routes; whole-product completeness unverified
Nutshell current REST contacts/accounts APIs and webhooks using customer Basic credentials; Enterprise read-only SQL is disclosed as a separate route.
Documented CRM entity records and list CSVs are portable; complete history/files remain unverified.
Nutshell API route overview ↗
REST API · Checked 2026-10-16
Business logic and customization
5% of the overall score before applicability adjustment.
Scored answers and evidence
Logic authoring 2.5/10
External integration code; native business logic portability not established
Nutshell current REST contacts/accounts APIs and webhooks using customer Basic credentials; Enterprise read-only SQL is disclosed as a separate route.
Custom integrations and reporting applications are explicitly supported.
Nutshell current REST availability ↗
What can I build · Checked 2026-10-16
Rights to custom logic -
-
Nutshell current REST contacts/accounts APIs and webhooks using customer Basic credentials; Enterprise read-only SQL is disclosed as a separate route.
Rights to native workflow artifacts and independent execution are not established.
Nutshell API route overview ↗
Reviewed product documentation; stated limitation not resolved · Checked 2026-10-16
Scores are out of 10. * Incomplete evidence discounts verified capabilities (unknown answers stay unknown). Planned migration drives data exit. Scoring method ↗
CUSTOMER CHOICE
Third-party accessibility
Customers create API keys in Setup. REST uses HTTPS Basic authentication with a Nutshell user email and the key; the legacy JSON-RPC interface is separate.
Confirm who can connect, who owns the credentials and which uses are permitted. Customer consent and provider approval can be separate requirements; the selected plan and contract still matter.
READ / INTEGRATE
API and export routes
The current guide documents entity reads/writes, lists, filters and reports. Saved lists can also export CSV; SQL access belongs to Enterprise and is not assumed for every REST customer.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| Customer REST API key | HTTP Basic | Customer | No | customer creates key in setup; user email plus key in http basic; rest access included | 2026-10-16 |
Availability depends on your product, plan and agreement. See the documentation below for the requirements of each route.
ECONOMIC ACCESS
Cost, authentication and limits
The provider’s June 2026 announcement says full API access is included for all customers. Enterprise adds SQL and API strategy support; a REST numeric throughput contract was not established.
Check API entitlement, credential ownership and rate limits for the route you intend to use. Include review fees, customer-plan upgrades and ongoing access charges in the total.
ACT FROM OUTSIDE
External action
The audience-management guide documents POST contact creation and PATCH membership changes. Replacement membership removes omitted audiences, so distinguish add/remove from replace.
Validate the supported operation, acting identity and permission scope (read access does not imply write permission). Ambiguous retries and revoked credentials also affect whether an external workflow can run safely.
KEEP ACCESS USEFUL
Continuity
Webhooks announce contact/company/lead/activity changes and other events. Their event list is expressly partial; complete deletion capture and retained event replay are unverified.
CDC, deletions and recovery
| Question | Answer / applicable route | Evidence |
|---|---|---|
| Can ongoing extraction identify updates and deleted records on the declared route? | Updates identified; deletion capture not establishedNutshell current REST contacts/accounts APIs and webhooks using customer Basic credentials; Enterprise read-only SQL is disclosed as a separate route. Webhook documentation establishes updates, but not exhaustive deletion identity coverage. | Nutshell webhooks ↗Qualifying events; partial-list warningChecked 2026-10-16 |
| How can extraction recover after missed events or an interrupted consumer? | Rebuild from a fresh snapshot; no historical replay establishedNutshell current REST contacts/accounts APIs and webhooks using customer Basic credentials; Enterprise read-only SQL is disclosed as a separate route. Repeat a saved-list export to rebuild its current selected records; no historical/deleted payload recovery established. | Nutshell current REST availability ↗Other integration pointsChecked 2026-10-16 |
Useful ongoing access includes corrections and deletions, not only the first export. A failed request, changed filter or lost resource permission should not be interpreted as a deleted record.
LEAVE WITH YOUR DATA
Data exit and portability
Structured REST records and saved-list CSVs support a scoped customer copy. Current-state lists do not establish complete attachments, historical events or an independent product restore.
Test the output against the destination’s required fields and history. Check stable identifiers, relationships, attachments and extraction time; a sample file proves only the coverage of that sample.
BUILD / INSPECT / REUSE
Business logic and customization
Customers can build external integrations and reporting apps. Native workflow artifact ownership and external execution remain unknown (API code is a separate artifact).
Custom API access, ownership of workflows and the right to export their definitions are separate questions. A custom-app capability alone does not establish that business rules can move to another system.
AGREEMENTS / API DOCS / PROGRAM REQUIREMENTS
Documented conditions
Answers below come from public provider materials. Every answer retains its source check date, scope (a partner agreement does not describe every customer route). Customer contracts and live behavior still need verification.
| Question | Answer / applicable route | Evidence |
|---|---|---|
| What structured read interface is documented? | Structured API for the declared product scopeNutshell current REST contacts/accounts APIs and webhooks using customer Basic credentials; Enterprise read-only SQL is disclosed as a separate route. REST supports retrieving standard CRM entities. | Nutshell API route overview ↗REST APIChecked 2026-10-16 |
| How can customers retrieve data in bulk? | Manual report downloadNutshell current REST contacts/accounts APIs and webhooks using customer Basic credentials; Enterprise read-only SQL is disclosed as a separate route. Saved Nutshell lists export CSV; REST collection pagination was not verified here. | Nutshell current REST availability ↗Other integration pointsChecked 2026-10-16 |
| What queries can a customer issue outside the provider UI? | Documented structured API filtersNutshell current REST contacts/accounts APIs and webhooks using customer Basic credentials; Enterprise read-only SQL is disclosed as a separate route. Current REST route supports lists, filters and reports. | Nutshell API route overview ↗REST APIChecked 2026-10-16 |
| Who decides whether a chosen third party may connect? | Customer authorization without discretionary provider approvalNutshell current REST contacts/accounts APIs and webhooks using customer Basic credentials; Enterprise read-only SQL is disclosed as a separate route. Customers build integrations and connect business systems through the open REST API. | Nutshell current REST availability ↗Why use a CRM API; getting startedChecked 2026-10-16 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | Access is free, or included in the lowest paid plan with no fixed access fee; published usage-only charges are eligibleNutshell current REST contacts/accounts APIs and webhooks using customer Basic credentials; Enterprise read-only SQL is disclosed as a separate route. Full API access has no additional charge for all customers; SQL is separate Enterprise scope. | Nutshell current REST availability ↗Quick answer; all plans FAQChecked 2026-10-16 |
| What permission is needed for the documented downstream use? | -Nutshell current REST contacts/accounts APIs and webhooks using customer Basic credentials; Enterprise read-only SQL is disclosed as a separate route. The reviewed technical documentation does not establish contractual permission for the declared downstream processing. | Nutshell API route overview ↗Reviewed product documentation; stated limitation not resolvedChecked 2026-10-16 |
| Which external write operations are documented? | Create and update in one business domainNutshell current REST contacts/accounts APIs and webhooks using customer Basic credentials; Enterprise read-only SQL is disclosed as a separate route. POST creates a contact and PATCH edits contact audience membership. | Nutshell contact creation and audience membership changes ↗Creating a person; Updating audience membershipChecked 2026-10-16 |
| How can customers connect an application they build or choose? | Customer applications using fixed APIs without provider selectionNutshell current REST contacts/accounts APIs and webhooks using customer Basic credentials; Enterprise read-only SQL is disclosed as a separate route. Customer API keys support custom apps and integrations. | Nutshell API authentication ↗API authenticationChecked 2026-10-16 |
| What mechanism supports repeatable extraction of changes? | Documented updated-since filters or webhooksNutshell current REST contacts/accounts APIs and webhooks using customer Basic credentials; Enterprise read-only SQL is disclosed as a separate route. Webhooks notify selected CRM record changes. | Nutshell webhooks ↗Qualifying eventsChecked 2026-10-16 |
| How are integration limits disclosed? | -Nutshell current REST contacts/accounts APIs and webhooks using customer Basic credentials; Enterprise read-only SQL is disclosed as a separate route. A numeric quota and recovery contract are not established by the reviewed route documentation. | Nutshell API route overview ↗Reviewed product documentation; stated limitation not resolvedChecked 2026-10-16 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsNutshell current REST contacts/accounts APIs and webhooks using customer Basic credentials; Enterprise read-only SQL is disclosed as a separate route. Saved lists download in CSV for external use. | Nutshell current REST availability ↗Other integration pointsChecked 2026-10-16 |
| What retrieval rights are documented at cancellation? | -Nutshell current REST contacts/accounts APIs and webhooks using customer Basic credentials; Enterprise read-only SQL is disclosed as a separate route. No retrieval window or export charge at cancellation is established by these technical sources. | Nutshell API route overview ↗Reviewed product documentation; stated limitation not resolvedChecked 2026-10-16 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedNutshell current REST contacts/accounts APIs and webhooks using customer Basic credentials; Enterprise read-only SQL is disclosed as a separate route. Custom integrations and reporting applications are explicitly supported. | Nutshell current REST availability ↗What can I buildChecked 2026-10-16 |
| What rights or portability are documented for custom workflow artifacts? | -Nutshell current REST contacts/accounts APIs and webhooks using customer Basic credentials; Enterprise read-only SQL is disclosed as a separate route. Rights to native workflow artifacts and independent execution are not established. | Nutshell API route overview ↗Reviewed product documentation; stated limitation not resolvedChecked 2026-10-16 |
| What usable data or native definitions can leave before cancellation? | Portable structured records on documented routes; whole-product completeness unverifiedNutshell current REST contacts/accounts APIs and webhooks using customer Basic credentials; Enterprise read-only SQL is disclosed as a separate route. Documented CRM entity records and list CSVs are portable; complete history/files remain unverified. | Nutshell API route overview ↗REST APIChecked 2026-10-16 |
SOURCES / SCOPE / HISTORY
Sources and open questions
This review is based on the documentation below. Live account behavior and customer-specific agreements haven’t been tested.
Still to confirm
- Lowest-plan API entitlement and fixed access fees
- Complete attachments/history and deletion recovery
- Native workflow rights and cancellation retrieval
Documentation
Assessment checked 2026-10-16. Each answer retains its source and applicable route; the check date does not establish live account behavior.