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
Dialpad / company shared-contact REST v2 list/create/update and contact events through a company-admin key; third-party OAuth registration is assessed separately. Call recordings, SMS and local-user contacts are excluded.
The contacts collection returns company shared-contact records.
Dialpad Contact List ↗
Contact List · Checked 2026-10-22
Bulk delivery 8.8/10
Batched or iterable API requests
Dialpad / company shared-contact REST v2 list/create/update and contact events through a company-admin key; third-party OAuth registration is assessed separately. Call recordings, SMS and local-user contacts are excluded.
Traverse cursor pages; omit limit or keep it at 100 or less.
Dialpad Contact List ↗
Cursor and soft-deprecated limit · Checked 2026-10-22
Query expressiveness 8.8/10
Documented structured API filters
Dialpad / company shared-contact REST v2 list/create/update and contact events through a company-admin key; third-party OAuth registration is assessed separately. Call recordings, SMS and local-user contacts are excluded.
The name parameter filters contacts; owner selection changes the contact scope.
Dialpad Contact List ↗
Query parameters · Checked 2026-10-22
Access cost barrier -
-
Dialpad / company shared-contact REST v2 list/create/update and contact events through a company-admin key; third-party OAuth registration is assessed separately. Call recordings, SMS and local-user contacts are excluded.
The key guide defers eligibility to pricing; exact plan and fees remain unverified.
Dialpad company-admin API keys ↗
Who can use this · Checked 2026-10-22
Third-party accessibility
20% of the overall score before applicability adjustment.
Scored answers and evidence
Third-party eligibility 5.0/10
Separate provider consent or partner agreement required
Dialpad / company shared-contact REST v2 list/create/update and contact events through a company-admin key; third-party OAuth registration is assessed separately. Call recordings, SMS and local-user contacts are excluded.
Third-party OAuth client credentials require registration with Dialpad; direct keys remain admin-managed.
Dialpad OAuth registration ↗
Register an OAuth application · Checked 2026-10-22
Downstream permission 7.5/10
Published purpose and confidentiality boundaries
Dialpad / company shared-contact REST v2 list/create/update and contact events through a company-admin key; third-party OAuth registration is assessed separately. Call recordings, SMS and local-user contacts are excluded.
Developer guidelines limit data to the app’s purpose and require customer terms and secure storage.
Dialpad developer usage guidelines ↗
Privacy and Security · Checked 2026-10-22
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
Dialpad / company shared-contact REST v2 list/create/update and contact events through a company-admin key; third-party OAuth registration is assessed separately. Call recordings, SMS and local-user contacts are excluded.
Shared contacts can be created and updated through the named operations.
Dialpad Contact Create ↗
Contact Create: owner_id · Checked 2026-10-22
Dialpad Contact Update ↗
Documented update operation · Checked 2026-10-22
Custom application path 10.0/10
Customer applications using fixed APIs without provider selection
Dialpad / company shared-contact REST v2 list/create/update and contact events through a company-admin key; third-party OAuth registration is assessed separately. Call recordings, SMS and local-user contacts are excluded.
Company admins can issue direct keys for customer applications; OAuth has a separate registration path.
Dialpad company-admin API keys ↗
Create an API key · Checked 2026-10-22
Continuity
15% of the overall score before applicability adjustment.
Scored answers and evidence
Refresh mechanism 7.5/10
Documented updated-since filters or webhooks
Dialpad / company shared-contact REST v2 list/create/update and contact events through a company-admin key; third-party OAuth registration is assessed separately. Call recordings, SMS and local-user contacts are excluded.
Contact event subscriptions notify a receiver about contact changes.
Dialpad Contact Events ↗
Contact Events · Checked 2026-10-22
Limit visibility 7.5/10
Numeric usage or polling guidance
Dialpad / company shared-contact REST v2 list/create/update and contact events through a company-admin key; third-party OAuth registration is assessed separately. Call recordings, SMS and local-user contacts are excluded.
Company traffic is limited to 20 requests/second; contact creation has a 100/minute limit.
Dialpad rate limits ↗
Rate Limits · Checked 2026-10-22
CDC and deletion capture 7.5/10
Updates and deletion identities documented for the stated resources
Dialpad / company shared-contact REST v2 list/create/update and contact events through a company-admin key; third-party OAuth registration is assessed separately. Call recordings, SMS and local-user contacts are excluded.
Created, Updated and Deleted events include a contact object and unique ID.
Dialpad Contact Events ↗
Payload event and contact.id · Checked 2026-10-22
Replay and gap recovery 2.5/10
Rebuild from a fresh snapshot; no historical replay established
Dialpad / company shared-contact REST v2 list/create/update and contact events through a company-admin key; third-party OAuth registration is assessed separately. Call recordings, SMS and local-user contacts are excluded.
Cursor scans can rebuild current shared contacts; retained events and deleted payloads are unverified.
Dialpad Contact List ↗
Contact List cursor traversal · Checked 2026-10-22
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
Dialpad / company shared-contact REST v2 list/create/update and contact events through a company-admin key; third-party OAuth registration is assessed separately. Call recordings, SMS and local-user contacts are excluded.
Scoped API records can be held outside the provider.
Dialpad Contact List ↗
Documented structured read response · Checked 2026-10-22
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
Dialpad / company shared-contact REST v2 list/create/update and contact events through a company-admin key; third-party OAuth registration is assessed separately. Call recordings, SMS and local-user contacts are excluded.
The reviewed access docs do not establish contractual retrieval rights after cancellation.
Dialpad company-admin API keys ↗
Access route; termination rights unresolved · Checked 2026-10-22
Planned migration fidelity 7.5/10
Portable structured records on documented routes; whole-product completeness unverified
Dialpad / company shared-contact REST v2 list/create/update and contact events through a company-admin key; third-party OAuth registration is assessed separately. Call recordings, SMS and local-user contacts are excluded.
Portable records are documented; complete native restore and history remain unverified.
Dialpad Contact List ↗
Read response and declared object scope · Checked 2026-10-22
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
Dialpad / company shared-contact REST v2 list/create/update and contact events through a company-admin key; third-party OAuth registration is assessed separately. Call recordings, SMS and local-user contacts are excluded.
External code can use the scoped API; native workflow portability is not established.
Dialpad company-admin API keys ↗
Application authentication · Checked 2026-10-22
Rights to custom logic -
-
Dialpad / company shared-contact REST v2 list/create/update and contact events through a company-admin key; third-party OAuth registration is assessed separately. Call recordings, SMS and local-user contacts are excluded.
Native workflow ownership and reusable export rights require a separate contractual review.
Dialpad company-admin API keys ↗
Access route; native artifact rights unresolved · Checked 2026-10-22
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
Company admins create expiring keys with selected scopes. Developers request OAuth client credentials through a registration form; an admin key does not prove public-app distribution eligibility.
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 use cursor pagination and name filters. Omit limit or keep it at 100 or less; larger values trigger deliberately intermittent 400 responses.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| Company-admin key for shared contacts | API key | Customer | No | Customer-supplied credentials | 2026-10-22 |
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 key guide directs customers to pricing for eligibility. Minimum plan and exact API fees for this contact route remain unresolved.
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
Create shared contacts by omitting owner_id; update existing contact fields through the contact update operation.
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
Contact events cover Created, Updated and Deleted with contact IDs. Signed notifications need a public receiver; retained replay and delivery-retry guarantees remain unverified.
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 resourcesDialpad / company shared-contact REST v2 list/create/update and contact events through a company-admin key; third-party OAuth registration is assessed separately. Call recordings, SMS and local-user contacts are excluded. Created, Updated and Deleted events include a contact object and unique ID. | Dialpad Contact Events ↗Payload event and contact.idChecked 2026-10-22 |
| How can extraction recover after missed events or an interrupted consumer? | Rebuild from a fresh snapshot; no historical replay establishedDialpad / company shared-contact REST v2 list/create/update and contact events through a company-admin key; third-party OAuth registration is assessed separately. Call recordings, SMS and local-user contacts are excluded. Cursor scans can rebuild current shared contacts; retained events and deleted payloads are unverified. | Dialpad Contact List ↗Contact List cursor traversalChecked 2026-10-22 |
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
Current shared-contact records can be retained outside Dialpad. They do not include call content, recordings or native routing rules.
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 write external integration code against the assessed API. Native workflow rights and independent execution remain unresolved (record access does not establish portable business logic).
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 scopeDialpad / company shared-contact REST v2 list/create/update and contact events through a company-admin key; third-party OAuth registration is assessed separately. Call recordings, SMS and local-user contacts are excluded. The contacts collection returns company shared-contact records. | Dialpad Contact List ↗Contact ListChecked 2026-10-22 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsDialpad / company shared-contact REST v2 list/create/update and contact events through a company-admin key; third-party OAuth registration is assessed separately. Call recordings, SMS and local-user contacts are excluded. Traverse cursor pages; omit limit or keep it at 100 or less. | Dialpad Contact List ↗Cursor and soft-deprecated limitChecked 2026-10-22 |
| What queries can a customer issue outside the provider UI? | Documented structured API filtersDialpad / company shared-contact REST v2 list/create/update and contact events through a company-admin key; third-party OAuth registration is assessed separately. Call recordings, SMS and local-user contacts are excluded. The name parameter filters contacts; owner selection changes the contact scope. | Dialpad Contact List ↗Query parametersChecked 2026-10-22 |
| Who decides whether a chosen third party may connect? | Separate provider consent or partner agreement requiredDialpad / company shared-contact REST v2 list/create/update and contact events through a company-admin key; third-party OAuth registration is assessed separately. Call recordings, SMS and local-user contacts are excluded. Third-party OAuth client credentials require registration with Dialpad; direct keys remain admin-managed. | Dialpad OAuth registration ↗Register an OAuth applicationChecked 2026-10-22 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -Dialpad / company shared-contact REST v2 list/create/update and contact events through a company-admin key; third-party OAuth registration is assessed separately. Call recordings, SMS and local-user contacts are excluded. The key guide defers eligibility to pricing; exact plan and fees remain unverified. | Dialpad company-admin API keys ↗Who can use thisChecked 2026-10-22 |
| What permission is needed for the documented downstream use? | Published purpose and confidentiality boundariesDialpad / company shared-contact REST v2 list/create/update and contact events through a company-admin key; third-party OAuth registration is assessed separately. Call recordings, SMS and local-user contacts are excluded. Developer guidelines limit data to the app’s purpose and require customer terms and secure storage. | Dialpad developer usage guidelines ↗Privacy and SecurityChecked 2026-10-22 |
| Which external write operations are documented? | Create and update in one business domainDialpad / company shared-contact REST v2 list/create/update and contact events through a company-admin key; third-party OAuth registration is assessed separately. Call recordings, SMS and local-user contacts are excluded. Shared contacts can be created and updated through the named operations. | Dialpad Contact Create ↗Contact Create: owner_idChecked 2026-10-22 Dialpad Contact Update ↗Documented update operationChecked 2026-10-22 |
| How can customers connect an application they build or choose? | Customer applications using fixed APIs without provider selectionDialpad / company shared-contact REST v2 list/create/update and contact events through a company-admin key; third-party OAuth registration is assessed separately. Call recordings, SMS and local-user contacts are excluded. Company admins can issue direct keys for customer applications; OAuth has a separate registration path. | Dialpad company-admin API keys ↗Create an API keyChecked 2026-10-22 |
| What mechanism supports repeatable extraction of changes? | Documented updated-since filters or webhooksDialpad / company shared-contact REST v2 list/create/update and contact events through a company-admin key; third-party OAuth registration is assessed separately. Call recordings, SMS and local-user contacts are excluded. Contact event subscriptions notify a receiver about contact changes. | Dialpad Contact Events ↗Contact EventsChecked 2026-10-22 |
| How are integration limits disclosed? | Numeric usage or polling guidanceDialpad / company shared-contact REST v2 list/create/update and contact events through a company-admin key; third-party OAuth registration is assessed separately. Call recordings, SMS and local-user contacts are excluded. Company traffic is limited to 20 requests/second; contact creation has a 100/minute limit. | Dialpad rate limits ↗Rate LimitsChecked 2026-10-22 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsDialpad / company shared-contact REST v2 list/create/update and contact events through a company-admin key; third-party OAuth registration is assessed separately. Call recordings, SMS and local-user contacts are excluded. Scoped API records can be held outside the provider. | Dialpad Contact List ↗Documented structured read responseChecked 2026-10-22 |
| What usable data or native definitions can leave before cancellation? | Portable structured records on documented routes; whole-product completeness unverifiedDialpad / company shared-contact REST v2 list/create/update and contact events through a company-admin key; third-party OAuth registration is assessed separately. Call recordings, SMS and local-user contacts are excluded. Portable records are documented; complete native restore and history remain unverified. | Dialpad Contact List ↗Read response and declared object scopeChecked 2026-10-22 |
| What retrieval rights are documented at cancellation? | -Dialpad / company shared-contact REST v2 list/create/update and contact events through a company-admin key; third-party OAuth registration is assessed separately. Call recordings, SMS and local-user contacts are excluded. The reviewed access docs do not establish contractual retrieval rights after cancellation. | Dialpad company-admin API keys ↗Access route; termination rights unresolvedChecked 2026-10-22 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedDialpad / company shared-contact REST v2 list/create/update and contact events through a company-admin key; third-party OAuth registration is assessed separately. Call recordings, SMS and local-user contacts are excluded. External code can use the scoped API; native workflow portability is not established. | Dialpad company-admin API keys ↗Application authenticationChecked 2026-10-22 |
| What rights or portability are documented for custom workflow artifacts? | -Dialpad / company shared-contact REST v2 list/create/update and contact events through a company-admin key; third-party OAuth registration is assessed separately. Call recordings, SMS and local-user contacts are excluded. Native workflow ownership and reusable export rights require a separate contractual review. | Dialpad company-admin API keys ↗Access route; native artifact rights unresolvedChecked 2026-10-22 |
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
- Minimum plan and exact customer or partner API fees
- Contact event retries and retained replay
- Applicable downstream terms where not established above
- Contractual post-cancellation retrieval rights
- Native workflow ownership, reusable definitions and complete product migration
Documentation
Assessment checked 2026-10-22. Each answer retains its source and applicable route; the check date does not establish live account behavior.