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
Copper Developer API / customer API key and user email; leads, people, companies, opportunities and supported webhooks. Partner-registered OAuth is a separate distribution route.
Structured records are available for the declared product scope.
Copper Developer API ↗
CRM resources and custom-field definitions · Checked 2026-10-16
Bulk delivery 8.8/10
Batched or iterable API requests
Copper Developer API / customer API key and user email; leads, people, companies, opportunities and supported webhooks. Partner-registered OAuth is a separate distribution route.
Iterable record queries provide bulk retrieval within endpoint limits; complete account recovery is unverified.
Copper Developer API ↗
CRM resources and custom-field definitions · Checked 2026-10-16
Query expressiveness 8.8/10
Documented structured API filters
Copper Developer API / customer API key and user email; leads, people, companies, opportunities and supported webhooks. Partner-registered OAuth is a separate distribution route.
Search filters including minimum_modified_date
List Leads (Search) ↗
Search filters including minimum_modified_date · Checked 2026-10-16
Access cost barrier -
-
Copper Developer API / customer API key and user email; leads, people, companies, opportunities and supported webhooks. Partner-registered OAuth is a separate distribution route.
Numeric request ceilings do not establish plan entitlement or fixed access fee
Requests and rate limits ↗
Reviewed route entitlement and plan conditions · 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
Copper Developer API / customer API key and user email; leads, people, companies, opportunities and supported webhooks. Partner-registered OAuth is a separate distribution route.
Customer-generated API keys; OAuth registration is separately gated
API key authentication ↗
Customer-generated API keys; OAuth registration is separately gated · Checked 2026-10-16
Downstream permission -
-
Copper Developer API / customer API key and user email; leads, people, companies, opportunities and supported webhooks. Partner-registered OAuth is a separate distribution route.
Downstream processing, AI and redistribution permission require a separate applicable-terms review.
API key authentication ↗
Authentication documentation reviewed; applicable downstream contractual clause not established · 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
Copper Developer API / customer API key and user email; leads, people, companies, opportunities and supported webhooks. Partner-registered OAuth is a separate distribution route.
Create and update leads, people, companies and opportunities
Copper Developer API ↗
Create and update leads, people, companies and opportunities · Checked 2026-10-16
Custom application path 10.0/10
Customer applications using fixed APIs without provider selection
Copper Developer API / customer API key and user email; leads, people, companies, opportunities and supported webhooks. Partner-registered OAuth is a separate distribution route.
Customer application authentication for the declared route
API key authentication ↗
Customer application authentication for the declared route · 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
Copper Developer API / customer API key and user email; leads, people, companies, opportunities and supported webhooks. Partner-registered OAuth is a separate distribution route.
minimum_modified_date search filter
List Leads (Search) ↗
minimum_modified_date search filter · Checked 2026-10-16
Limit visibility 7.5/10
Numeric usage or polling guidance
Copper Developer API / customer API key and user email; leads, people, companies, opportunities and supported webhooks. Partner-registered OAuth is a separate distribution route.
Numeric rolling API and bulk ceilings plus 429 errors are documented; a precise retry-delay contract was not established.
Requests and rate limits ↗
Published numeric limits, rate-limit errors and recovery information · Checked 2026-10-16
CDC and deletion capture 7.5/10
Updates and deletion identities documented for the stated resources
Copper Developer API / customer API key and user email; leads, people, companies, opportunities and supported webhooks. Partner-registered OAuth is a separate distribution route.
Supported entities, create/update/delete notifications and record IDs; exclusions for relationship and metadata changes
Webhooks overview ↗
Supported entities, create/update/delete notifications and record IDs; exclusions for relationship and metadata changes · Checked 2026-10-16
Replay and gap recovery 2.5/10
Rebuild from a fresh snapshot; no historical replay established
Copper Developer API / customer API key and user email; leads, people, companies, opportunities and supported webhooks. Partner-registered OAuth is a separate distribution route.
Paginated current-state retrieval; webhook guide expressly excludes retries
Paginating search results ↗
Paginated current-state retrieval; webhook guide expressly excludes retries · 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
Copper Developer API / customer API key and user email; leads, people, companies, opportunities and supported webhooks. Partner-registered OAuth is a separate distribution route.
Customer-held API records are documented; no whole-product custody claim is made.
Copper Developer API ↗
CRM resources and custom-field definitions · Checked 2026-10-16
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
Copper Developer API / customer API key and user email; leads, people, companies, opportunities and supported webhooks. Partner-registered OAuth is a separate distribution route.
Post-cancellation retrieval remains unresolved.
API key authentication ↗
Reviewed technical route; applicable customer termination clause not established · Checked 2026-10-16
Planned migration fidelity 7.5/10
Portable structured records on documented routes; whole-product completeness unverified
Copper Developer API / customer API key and user email; leads, people, companies, opportunities and supported webhooks. Partner-registered OAuth is a separate distribution route.
Portable records within the declared API scope; complete attachments, history and service configuration are unverified.
Copper Developer API ↗
CRM resources and custom-field definitions · 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
Copper Developer API / customer API key and user email; leads, people, companies, opportunities and supported webhooks. Partner-registered OAuth is a separate distribution route.
Build customer applications through Developer API
Copper Developer API ↗
Build customer applications through Developer API · Checked 2026-10-16
Rights to custom logic -
-
Copper Developer API / customer API key and user email; leads, people, companies, opportunities and supported webhooks. Partner-registered OAuth is a separate distribution route.
Rights to native workflow definitions remain unresolved.
API key authentication ↗
Reviewed technical route; native artifact ownership and export rights not established · 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 generate labeled API keys in settings and include the key owner’s email with requests. Copper’s OAuth route requires contacting its partner team to register the application; customer-key access and partner OAuth have different gates.
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
REST exposes CRM records and custom-field definitions. Search pages contain up to 200 records and stop at 100,000 matches, requiring partitions for larger selections. Leads and opportunities expose modified-date filters; native database snapshots remain unverified.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| Customer-authorized API access | API key | Customer | No | Customer-supplied credentials | 2026-10-16 |
| Third-party OAuth application | OAuth 2.0 | Integration provider | Yes | Partner approval | 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 API documents a rolling 180-request-per-minute ceiling and an additional three-per-second bulk ceiling. Current minimum-plan entitlement and any fixed API fee remain unresolved; a partner registration process does not establish its price.
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
REST supports creating and updating CRM records. API keys require explicit permission review before use; OAuth currently exposes one broad developer/v1/all scope for read and modify access.
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
Supported webhooks identify record creates, updates and deletes, but Copper sends each notification at most once and never retries. Update notifications exclude relationship and metadata changes; periodic REST reconciliation remains necessary.
CDC, deletions and recovery
| Question | Answer / applicable route | Evidence |
|---|---|---|
| Can ongoing extraction identify updates and deleted records on the declared route? | Updates and deletion identities documented for the stated resourcesCopper Developer API / customer API key and user email; leads, people, companies, opportunities and supported webhooks. Partner-registered OAuth is a separate distribution route. Supported entities, create/update/delete notifications and record IDs; exclusions for relationship and metadata changes | Webhooks overview ↗Supported entities, create/update/delete notifications and record IDs; exclusions for relationship and metadata changesChecked 2026-10-16 |
| How can extraction recover after missed events or an interrupted consumer? | Rebuild from a fresh snapshot; no historical replay establishedCopper Developer API / customer API key and user email; leads, people, companies, opportunities and supported webhooks. Partner-registered OAuth is a separate distribution route. Paginated current-state retrieval; webhook guide expressly excludes retries | Paginating search results ↗Paginated current-state retrieval; webhook guide expressly excludes retriesChecked 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
Paginated CRM records provide an external structured copy before cancellation. Missing notifications can be repaired with current-state extraction, while earlier states and deleted payloads may be unrecoverable. Complete files, mail and cancellation rights remain unverified.
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
Customer applications can run external code through fixed REST interfaces. The reviewed documents do not establish ownership or independent execution of native workflow artifacts (API client code cannot establish those rights).
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 scopeCopper Developer API / customer API key and user email; leads, people, companies, opportunities and supported webhooks. Partner-registered OAuth is a separate distribution route. Structured records are available for the declared product scope. | Copper Developer API ↗CRM resources and custom-field definitionsChecked 2026-10-16 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsCopper Developer API / customer API key and user email; leads, people, companies, opportunities and supported webhooks. Partner-registered OAuth is a separate distribution route. Iterable record queries provide bulk retrieval within endpoint limits; complete account recovery is unverified. | Copper Developer API ↗CRM resources and custom-field definitionsChecked 2026-10-16 |
| What queries can a customer issue outside the provider UI? | Documented structured API filtersCopper Developer API / customer API key and user email; leads, people, companies, opportunities and supported webhooks. Partner-registered OAuth is a separate distribution route. Search filters including minimum_modified_date | List Leads (Search) ↗Search filters including minimum_modified_dateChecked 2026-10-16 |
| Who decides whether a chosen third party may connect? | Customer authorization without discretionary provider approvalCopper Developer API / customer API key and user email; leads, people, companies, opportunities and supported webhooks. Partner-registered OAuth is a separate distribution route. Customer-generated API keys; OAuth registration is separately gated | API key authentication ↗Customer-generated API keys; OAuth registration is separately gatedChecked 2026-10-16 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -Copper Developer API / customer API key and user email; leads, people, companies, opportunities and supported webhooks. Partner-registered OAuth is a separate distribution route. Numeric request ceilings do not establish plan entitlement or fixed access fee | Requests and rate limits ↗Reviewed route entitlement and plan conditionsChecked 2026-10-16 |
| What permission is needed for the documented downstream use? | -Copper Developer API / customer API key and user email; leads, people, companies, opportunities and supported webhooks. Partner-registered OAuth is a separate distribution route. Downstream processing, AI and redistribution permission require a separate applicable-terms review. | API key authentication ↗Authentication documentation reviewed; applicable downstream contractual clause not establishedChecked 2026-10-16 |
| Which external write operations are documented? | Create and update in one business domainCopper Developer API / customer API key and user email; leads, people, companies, opportunities and supported webhooks. Partner-registered OAuth is a separate distribution route. Create and update leads, people, companies and opportunities | Copper Developer API ↗Create and update leads, people, companies and opportunitiesChecked 2026-10-16 |
| How can customers connect an application they build or choose? | Customer applications using fixed APIs without provider selectionCopper Developer API / customer API key and user email; leads, people, companies, opportunities and supported webhooks. Partner-registered OAuth is a separate distribution route. Customer application authentication for the declared route | API key authentication ↗Customer application authentication for the declared routeChecked 2026-10-16 |
| What mechanism supports repeatable extraction of changes? | Documented updated-since filters or webhooksCopper Developer API / customer API key and user email; leads, people, companies, opportunities and supported webhooks. Partner-registered OAuth is a separate distribution route. minimum_modified_date search filter | List Leads (Search) ↗minimum_modified_date search filterChecked 2026-10-16 |
| How are integration limits disclosed? | Numeric usage or polling guidanceCopper Developer API / customer API key and user email; leads, people, companies, opportunities and supported webhooks. Partner-registered OAuth is a separate distribution route. Numeric rolling API and bulk ceilings plus 429 errors are documented; a precise retry-delay contract was not established. | Requests and rate limits ↗Published numeric limits, rate-limit errors and recovery informationChecked 2026-10-16 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsCopper Developer API / customer API key and user email; leads, people, companies, opportunities and supported webhooks. Partner-registered OAuth is a separate distribution route. Customer-held API records are documented; no whole-product custody claim is made. | Copper Developer API ↗CRM resources and custom-field definitionsChecked 2026-10-16 |
| What retrieval rights are documented at cancellation? | -Copper Developer API / customer API key and user email; leads, people, companies, opportunities and supported webhooks. Partner-registered OAuth is a separate distribution route. Post-cancellation retrieval remains unresolved. | API key authentication ↗Reviewed technical route; applicable customer termination clause not establishedChecked 2026-10-16 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedCopper Developer API / customer API key and user email; leads, people, companies, opportunities and supported webhooks. Partner-registered OAuth is a separate distribution route. Build customer applications through Developer API | Copper Developer API ↗Build customer applications through Developer APIChecked 2026-10-16 |
| What rights or portability are documented for custom workflow artifacts? | -Copper Developer API / customer API key and user email; leads, people, companies, opportunities and supported webhooks. Partner-registered OAuth is a separate distribution route. Rights to native workflow definitions remain unresolved. | API key authentication ↗Reviewed technical route; native artifact ownership and export rights not establishedChecked 2026-10-16 |
| What usable data or native definitions can leave before cancellation? | Portable structured records on documented routes; whole-product completeness unverifiedCopper Developer API / customer API key and user email; leads, people, companies, opportunities and supported webhooks. Partner-registered OAuth is a separate distribution route. Portable records within the declared API scope; complete attachments, history and service configuration are unverified. | Copper Developer API ↗CRM resources and custom-field definitionsChecked 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
- Current lowest-plan API entitlement and fees
- API-key permission boundaries for the intended account
- Downstream-use and cancellation clauses
- Native workflow ownership and export
- Historical recovery after a missed deletion
Documentation
Assessment checked 2026-10-16. Each answer retains its source and applicable route; the check date does not establish live account behavior.