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
Insightly CRM REST v3.1 user-key API, contact collection reads/search and contact mutations; email-associated attachments are excluded by the reference.
Contacts and other CRM entities return JSON.
Insightly REST v3.1 reference ↗
Objects · Checked 2026-10-16
Bulk delivery 8.8/10
Batched or iterable API requests
Insightly CRM REST v3.1 user-key API, contact collection reads/search and contact mutations; email-associated attachments are excluded by the reference.
top/skip traversal has default 100 and maximum 500 rows per page.
Insightly REST v3.1 reference ↗
Limiting Returned Records · Checked 2026-10-16
Query expressiveness 8.8/10
Documented structured API filters
Insightly CRM REST v3.1 user-key API, contact collection reads/search and contact mutations; email-associated attachments are excluded by the reference.
Search supports field/value and updated_after_utc predicates.
Insightly REST v3.1 reference ↗
Searching and Filtering; Date Formatting · 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
Insightly CRM REST v3.1 user-key API, contact collection reads/search and contact mutations; email-associated attachments are excluded by the reference.
The reference explicitly enables API queries/updates on all plans.
Insightly REST v3.1 reference ↗
Overview · 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
Insightly CRM REST v3.1 user-key API, contact collection reads/search and contact mutations; email-associated attachments are excluded by the reference.
User credentials support integration with external systems and applications.
Insightly REST v3.1 reference ↗
Introduction; Authentication · Checked 2026-10-16
Downstream permission -
-
Insightly CRM REST v3.1 user-key API, contact collection reads/search and contact mutations; email-associated attachments are excluded by the reference.
The reviewed technical documentation does not establish contractual permission for the declared downstream processing.
Insightly REST v3.1 reference ↗
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
Insightly CRM REST v3.1 user-key API, contact collection reads/search and contact mutations; email-associated attachments are excluded by the reference.
The reference documents POST contact creation and PUT contact/custom-field updates.
Insightly REST v3.1 reference ↗
Write/Update Requests; Custom Fields · Checked 2026-10-16
Custom application path 10.0/10
Customer applications using fixed APIs without provider selection
Insightly CRM REST v3.1 user-key API, contact collection reads/search and contact mutations; email-associated attachments are excluded by the reference.
Customer API keys support external applications with user-equivalent permissions.
Insightly REST v3.1 reference ↗
Introduction; 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
Insightly CRM REST v3.1 user-key API, contact collection reads/search and contact mutations; email-associated attachments are excluded by the reference.
updated_after_utc filters identify modified records.
Insightly REST v3.1 reference ↗
Date Formatting · Checked 2026-10-16
Limit visibility 10.0/10
Published numeric quotas and recovery instructions
Insightly CRM REST v3.1 user-key API, contact collection reads/search and contact mutations; email-associated attachments are excluded by the reference.
Numeric per-second/daily budgets, quota headers and 429 recovery are published.
Insightly REST v3.1 reference ↗
Rate Limiting / Throttling Requests; Rate Limit Response Header · Checked 2026-10-16
CDC and deletion capture 5.0/10
Updates identified; deletion capture not established
Insightly CRM REST v3.1 user-key API, contact collection reads/search and contact mutations; email-associated attachments are excluded by the reference.
Updated-time search is documented; no deletion feed established.
Insightly REST v3.1 reference ↗
Date Formatting · Checked 2026-10-16
Replay and gap recovery 2.5/10
Rebuild from a fresh snapshot; no historical replay established
Insightly CRM REST v3.1 user-key API, contact collection reads/search and contact mutations; email-associated attachments are excluded by the reference.
Repeat contact pagination rebuilds current authorized records, not deleted payloads or prior versions.
Insightly REST v3.1 reference ↗
Limiting Returned Records · 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
Insightly CRM REST v3.1 user-key API, contact collection reads/search and contact mutations; email-associated attachments are excluded by the reference.
Contact JSON can be received outside the provider.
Insightly REST v3.1 reference ↗
Example API Call · Checked 2026-10-16
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
Insightly CRM REST v3.1 user-key API, contact collection reads/search and contact mutations; email-associated attachments are excluded by the reference.
No retrieval window or export charge at cancellation is established by these technical sources.
Insightly REST v3.1 reference ↗
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
Insightly CRM REST v3.1 user-key API, contact collection reads/search and contact mutations; email-associated attachments are excluded by the reference.
Portable CRM records; files linked to email are excluded and full history unresolved.
Insightly REST v3.1 reference ↗
Objects; Troubleshooting Tips · 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
Insightly CRM REST v3.1 user-key API, contact collection reads/search and contact mutations; email-associated attachments are excluded by the reference.
The API enables customer integrations with external systems.
Insightly REST v3.1 reference ↗
Introduction · Checked 2026-10-16
Rights to custom logic -
-
Insightly CRM REST v3.1 user-key API, contact collection reads/search and contact mutations; email-associated attachments are excluded by the reference.
Rights to native workflow artifacts and independent execution are not established.
Insightly REST v3.1 reference ↗
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
A customer user obtains the API key and pod URL in User Settings. Basic authentication uses the key as username and no password; API visibility and edits match that user.
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
Contacts return paginated JSON with top/skip, default 100 and maximum 500 per response. Search supports standard/custom fields and updated_after_utc.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| Customer user API key | HTTP Basic | Customer | No | user settings api key and pod url; api key as basic username; permissions follow user | 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 v3.1 reference says all plans can query and update data. It lists 10 requests/second and plan-specific daily allowances with X-RateLimit headers and 429 behavior.
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
Contact creation uses POST; PUT updates supplied fields. Conditional PUT accepts If-Match with the current ETag and rejects a mismatch with 412.
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
Updated-time searches support overlapping polls. Hard deletion events and retained historical replay are unverified; a fresh contact traversal rebuilds only current authorized records.
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 establishedInsightly CRM REST v3.1 user-key API, contact collection reads/search and contact mutations; email-associated attachments are excluded by the reference. Updated-time search is documented; no deletion feed established. | Insightly REST v3.1 reference ↗Date FormattingChecked 2026-10-16 |
| How can extraction recover after missed events or an interrupted consumer? | Rebuild from a fresh snapshot; no historical replay establishedInsightly CRM REST v3.1 user-key API, contact collection reads/search and contact mutations; email-associated attachments are excluded by the reference. Repeat contact pagination rebuilds current authorized records, not deleted payloads or prior versions. | Insightly REST v3.1 reference ↗Limiting Returned RecordsChecked 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
Contact JSON is portable, but the reference excludes files associated with email. Whole-account history and service configuration are not proven by contact enumeration.
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 applications against fixed REST interfaces. Native automation rights and cancellation retrieval remain unresolved (the API is not a workflow export contract).
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 scopeInsightly CRM REST v3.1 user-key API, contact collection reads/search and contact mutations; email-associated attachments are excluded by the reference. Contacts and other CRM entities return JSON. | Insightly REST v3.1 reference ↗ObjectsChecked 2026-10-16 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsInsightly CRM REST v3.1 user-key API, contact collection reads/search and contact mutations; email-associated attachments are excluded by the reference. top/skip traversal has default 100 and maximum 500 rows per page. | Insightly REST v3.1 reference ↗Limiting Returned RecordsChecked 2026-10-16 |
| What queries can a customer issue outside the provider UI? | Documented structured API filtersInsightly CRM REST v3.1 user-key API, contact collection reads/search and contact mutations; email-associated attachments are excluded by the reference. Search supports field/value and updated_after_utc predicates. | Insightly REST v3.1 reference ↗Searching and Filtering; Date FormattingChecked 2026-10-16 |
| Who decides whether a chosen third party may connect? | Customer authorization without discretionary provider approvalInsightly CRM REST v3.1 user-key API, contact collection reads/search and contact mutations; email-associated attachments are excluded by the reference. User credentials support integration with external systems and applications. | Insightly REST v3.1 reference ↗Introduction; AuthenticationChecked 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 eligibleInsightly CRM REST v3.1 user-key API, contact collection reads/search and contact mutations; email-associated attachments are excluded by the reference. The reference explicitly enables API queries/updates on all plans. | Insightly REST v3.1 reference ↗OverviewChecked 2026-10-16 |
| What permission is needed for the documented downstream use? | -Insightly CRM REST v3.1 user-key API, contact collection reads/search and contact mutations; email-associated attachments are excluded by the reference. The reviewed technical documentation does not establish contractual permission for the declared downstream processing. | Insightly REST v3.1 reference ↗Reviewed product documentation; stated limitation not resolvedChecked 2026-10-16 |
| Which external write operations are documented? | Create and update in one business domainInsightly CRM REST v3.1 user-key API, contact collection reads/search and contact mutations; email-associated attachments are excluded by the reference. The reference documents POST contact creation and PUT contact/custom-field updates. | Insightly REST v3.1 reference ↗Write/Update Requests; Custom FieldsChecked 2026-10-16 |
| How can customers connect an application they build or choose? | Customer applications using fixed APIs without provider selectionInsightly CRM REST v3.1 user-key API, contact collection reads/search and contact mutations; email-associated attachments are excluded by the reference. Customer API keys support external applications with user-equivalent permissions. | Insightly REST v3.1 reference ↗Introduction; AuthenticationChecked 2026-10-16 |
| What mechanism supports repeatable extraction of changes? | Documented updated-since filters or webhooksInsightly CRM REST v3.1 user-key API, contact collection reads/search and contact mutations; email-associated attachments are excluded by the reference. updated_after_utc filters identify modified records. | Insightly REST v3.1 reference ↗Date FormattingChecked 2026-10-16 |
| How are integration limits disclosed? | Published numeric quotas and recovery instructionsInsightly CRM REST v3.1 user-key API, contact collection reads/search and contact mutations; email-associated attachments are excluded by the reference. Numeric per-second/daily budgets, quota headers and 429 recovery are published. | Insightly REST v3.1 reference ↗Rate Limiting / Throttling Requests; Rate Limit Response HeaderChecked 2026-10-16 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsInsightly CRM REST v3.1 user-key API, contact collection reads/search and contact mutations; email-associated attachments are excluded by the reference. Contact JSON can be received outside the provider. | Insightly REST v3.1 reference ↗Example API CallChecked 2026-10-16 |
| What retrieval rights are documented at cancellation? | -Insightly CRM REST v3.1 user-key API, contact collection reads/search and contact mutations; email-associated attachments are excluded by the reference. No retrieval window or export charge at cancellation is established by these technical sources. | Insightly REST v3.1 reference ↗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 establishedInsightly CRM REST v3.1 user-key API, contact collection reads/search and contact mutations; email-associated attachments are excluded by the reference. The API enables customer integrations with external systems. | Insightly REST v3.1 reference ↗IntroductionChecked 2026-10-16 |
| What rights or portability are documented for custom workflow artifacts? | -Insightly CRM REST v3.1 user-key API, contact collection reads/search and contact mutations; email-associated attachments are excluded by the reference. Rights to native workflow artifacts and independent execution are not established. | Insightly REST v3.1 reference ↗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 unverifiedInsightly CRM REST v3.1 user-key API, contact collection reads/search and contact mutations; email-associated attachments are excluded by the reference. Portable CRM records; files linked to email are excluded and full history unresolved. | Insightly REST v3.1 reference ↗Objects; Troubleshooting TipsChecked 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.