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
Aircall / shared-contact REST API list/create/update and contact webhooks; customer-private Basic authentication and approved partner OAuth have distinct eligibility. Call content and recordings are excluded.
Structured shared contacts include phone and email fields.
Aircall REST contacts, pagination and limits ↗
Contact: List all Contacts · Checked 2026-10-22
Bulk delivery 8.8/10
Batched or iterable API requests
Aircall / shared-contact REST API list/create/update and contact webhooks; customer-private Basic authentication and approved partner OAuth have distinct eligibility. Call content and recordings are excluded.
Pagination stops at 10,000 contacts; creation-date partitions are needed beyond that ceiling.
Aircall REST contacts, pagination and limits ↗
List all Contacts: from/to and pagination ceiling · Checked 2026-10-22
Query expressiveness 8.8/10
Documented structured API filters
Aircall / shared-contact REST API list/create/update and contact webhooks; customer-private Basic authentication and approved partner OAuth have distinct eligibility. Call content and recordings are excluded.
from/to filter creation dates; updated_at sorting does not establish a delta filter.
Aircall REST contacts, pagination and limits ↗
List all Contacts query parameters · Checked 2026-10-22
Access cost barrier -
-
Aircall / shared-contact REST API list/create/update and contact webhooks; customer-private Basic authentication and approved partner OAuth have distinct eligibility. Call content and recordings are excluded.
No minimum subscription or exact API fee was established for this route.
Aircall REST contacts, pagination and limits ↗
REST API; commercial entitlement unresolved · 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
Aircall / shared-contact REST API list/create/update and contact webhooks; customer-private Basic authentication and approved partner OAuth have distinct eligibility. Call content and recordings are excluded.
Multi-customer OAuth integrations require approved technology-partner status; private customer keys are separate.
Aircall customer and partner authentication ↗
When to use OAuth · Checked 2026-10-22
Downstream permission -
-
Aircall / shared-contact REST API list/create/update and contact webhooks; customer-private Basic authentication and approved partner OAuth have distinct eligibility. Call content and recordings are excluded.
Applicable processing, AI-use and redistribution terms remain unresolved.
Aircall customer and partner authentication ↗
Access route; downstream rights unresolved · 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
Aircall / shared-contact REST API list/create/update and contact webhooks; customer-private Basic authentication and approved partner OAuth have distinct eligibility. Call content and recordings are excluded.
Shared contacts support create and profile update; phone/email mutations are separate.
Aircall REST contacts, pagination and limits ↗
Create a Contact and Update a Contact · Checked 2026-10-22
Custom application path 10.0/10
Customer applications using fixed APIs without provider selection
Aircall / shared-contact REST API list/create/update and contact webhooks; customer-private Basic authentication and approved partner OAuth have distinct eligibility. Call content and recordings are excluded.
Private customer integrations use dashboard credentials; public distribution has a separate partner gate.
Aircall customer and partner authentication ↗
When to use Basic Authentication · 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
Aircall / shared-contact REST API list/create/update and contact webhooks; customer-private Basic authentication and approved partner OAuth have distinct eligibility. Call content and recordings are excluded.
Subscribe to contact-created, updated and deleted notifications.
Aircall webhook registration and verification ↗
Create a Webhook via the API and event selection · Checked 2026-10-22
Limit visibility 10.0/10
Published numeric quotas and recovery instructions
Aircall / shared-contact REST API list/create/update and contact webhooks; customer-private Basic authentication and approved partner OAuth have distinct eligibility. Call content and recordings are excluded.
The company budget is 120 requests/minute with limit/reset headers.
Aircall REST contacts, pagination and limits ↗
Rate limiting · Checked 2026-10-22
CDC and deletion capture 7.5/10
Updates and deletion identities documented for the stated resources
Aircall / shared-contact REST API list/create/update and contact webhooks; customer-private Basic authentication and approved partner OAuth have distinct eligibility. Call content and recordings are excluded.
Contact update and deletion events identify affected contacts.
Aircall REST contacts, pagination and limits ↗
Contact events: contact.updated and contact.deleted · Checked 2026-10-22
Replay and gap recovery 5.0/10
Bounded redelivery or overlapping queries; no durable consumer checkpoint
Aircall / shared-contact REST API list/create/update and contact webhooks; customer-private Basic authentication and approved partner OAuth have distinct eligibility. Call content and recordings are excluded.
Failed delivery is retried up to 50 times before disabling; no durable replay is established.
Aircall REST contacts, pagination and limits ↗
Webhook usage: Automatic deactivation · 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
Aircall / shared-contact REST API list/create/update and contact webhooks; customer-private Basic authentication and approved partner OAuth have distinct eligibility. Call content and recordings are excluded.
Scoped API records can be held outside the provider.
Aircall REST contacts, pagination and limits ↗
Documented structured read response · Checked 2026-10-22
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
Aircall / shared-contact REST API list/create/update and contact webhooks; customer-private Basic authentication and approved partner OAuth have distinct eligibility. Call content and recordings are excluded.
The reviewed access docs do not establish contractual retrieval rights after cancellation.
Aircall customer and partner authentication ↗
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
Aircall / shared-contact REST API list/create/update and contact webhooks; customer-private Basic authentication and approved partner OAuth have distinct eligibility. Call content and recordings are excluded.
Portable records are documented; complete native restore and history remain unverified.
Aircall REST contacts, pagination and limits ↗
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
Aircall / shared-contact REST API list/create/update and contact webhooks; customer-private Basic authentication and approved partner OAuth have distinct eligibility. Call content and recordings are excluded.
External code can use the scoped API; native workflow portability is not established.
Aircall customer and partner authentication ↗
Application authentication · Checked 2026-10-22
Rights to custom logic -
-
Aircall / shared-contact REST API list/create/update and contact webhooks; customer-private Basic authentication and approved partner OAuth have distinct eligibility. Call content and recordings are excluded.
Native workflow ownership and reusable export rights require a separate contractual review.
Aircall customer and partner authentication ↗
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
Customers use dashboard credentials for private integrations. Apps serving multiple customers use OAuth as approved technology partners.
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
Traverse contact pages and partition large sets with from/to creation dates. Sorting by updated_at is not a documented updated-since filter.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| Customer-private Basic-auth shared contacts | HTTP Basic | 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 API reference publishes request limits, but minimum subscription entitlement and exact customer or partner charges remain unconfirmed.
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 and update their profile fields. Phone and email changes use separate operations.
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 webhooks include creation, update and deletion. Up to 50 retries precede automatic disabling; duplicates and out-of-order delivery remain possible.
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 resourcesAircall / shared-contact REST API list/create/update and contact webhooks; customer-private Basic authentication and approved partner OAuth have distinct eligibility. Call content and recordings are excluded. Contact update and deletion events identify affected contacts. | Aircall REST contacts, pagination and limits ↗Contact events: contact.updated and contact.deletedChecked 2026-10-22 |
| How can extraction recover after missed events or an interrupted consumer? | Bounded redelivery or overlapping queries; no durable consumer checkpointAircall / shared-contact REST API list/create/update and contact webhooks; customer-private Basic authentication and approved partner OAuth have distinct eligibility. Call content and recordings are excluded. Failed delivery is retried up to 50 times before disabling; no durable replay is established. | Aircall REST contacts, pagination and limits ↗Webhook usage: Automatic deactivationChecked 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
Shared-contact JSON is portable within the documented collection bounds. Call recordings, conversation artifacts and complete account configuration require separate extraction.
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 scopeAircall / shared-contact REST API list/create/update and contact webhooks; customer-private Basic authentication and approved partner OAuth have distinct eligibility. Call content and recordings are excluded. Structured shared contacts include phone and email fields. | Aircall REST contacts, pagination and limits ↗Contact: List all ContactsChecked 2026-10-22 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsAircall / shared-contact REST API list/create/update and contact webhooks; customer-private Basic authentication and approved partner OAuth have distinct eligibility. Call content and recordings are excluded. Pagination stops at 10,000 contacts; creation-date partitions are needed beyond that ceiling. | Aircall REST contacts, pagination and limits ↗List all Contacts: from/to and pagination ceilingChecked 2026-10-22 |
| What queries can a customer issue outside the provider UI? | Documented structured API filtersAircall / shared-contact REST API list/create/update and contact webhooks; customer-private Basic authentication and approved partner OAuth have distinct eligibility. Call content and recordings are excluded. from/to filter creation dates; updated_at sorting does not establish a delta filter. | Aircall REST contacts, pagination and limits ↗List all Contacts query parametersChecked 2026-10-22 |
| Who decides whether a chosen third party may connect? | Separate provider consent or partner agreement requiredAircall / shared-contact REST API list/create/update and contact webhooks; customer-private Basic authentication and approved partner OAuth have distinct eligibility. Call content and recordings are excluded. Multi-customer OAuth integrations require approved technology-partner status; private customer keys are separate. | Aircall customer and partner authentication ↗When to use OAuthChecked 2026-10-22 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -Aircall / shared-contact REST API list/create/update and contact webhooks; customer-private Basic authentication and approved partner OAuth have distinct eligibility. Call content and recordings are excluded. No minimum subscription or exact API fee was established for this route. | Aircall REST contacts, pagination and limits ↗REST API; commercial entitlement unresolvedChecked 2026-10-22 |
| Which external write operations are documented? | Create and update in one business domainAircall / shared-contact REST API list/create/update and contact webhooks; customer-private Basic authentication and approved partner OAuth have distinct eligibility. Call content and recordings are excluded. Shared contacts support create and profile update; phone/email mutations are separate. | Aircall REST contacts, pagination and limits ↗Create a Contact and Update a ContactChecked 2026-10-22 |
| How can customers connect an application they build or choose? | Customer applications using fixed APIs without provider selectionAircall / shared-contact REST API list/create/update and contact webhooks; customer-private Basic authentication and approved partner OAuth have distinct eligibility. Call content and recordings are excluded. Private customer integrations use dashboard credentials; public distribution has a separate partner gate. | Aircall customer and partner authentication ↗When to use Basic AuthenticationChecked 2026-10-22 |
| What mechanism supports repeatable extraction of changes? | Documented updated-since filters or webhooksAircall / shared-contact REST API list/create/update and contact webhooks; customer-private Basic authentication and approved partner OAuth have distinct eligibility. Call content and recordings are excluded. Subscribe to contact-created, updated and deleted notifications. | Aircall webhook registration and verification ↗Create a Webhook via the API and event selectionChecked 2026-10-22 |
| How are integration limits disclosed? | Published numeric quotas and recovery instructionsAircall / shared-contact REST API list/create/update and contact webhooks; customer-private Basic authentication and approved partner OAuth have distinct eligibility. Call content and recordings are excluded. The company budget is 120 requests/minute with limit/reset headers. | Aircall REST contacts, pagination and limits ↗Rate limitingChecked 2026-10-22 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsAircall / shared-contact REST API list/create/update and contact webhooks; customer-private Basic authentication and approved partner OAuth have distinct eligibility. Call content and recordings are excluded. Scoped API records can be held outside the provider. | Aircall REST contacts, pagination and limits ↗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 unverifiedAircall / shared-contact REST API list/create/update and contact webhooks; customer-private Basic authentication and approved partner OAuth have distinct eligibility. Call content and recordings are excluded. Portable records are documented; complete native restore and history remain unverified. | Aircall REST contacts, pagination and limits ↗Read response and declared object scopeChecked 2026-10-22 |
| What retrieval rights are documented at cancellation? | -Aircall / shared-contact REST API list/create/update and contact webhooks; customer-private Basic authentication and approved partner OAuth have distinct eligibility. Call content and recordings are excluded. The reviewed access docs do not establish contractual retrieval rights after cancellation. | Aircall customer and partner authentication ↗Access route; termination rights unresolvedChecked 2026-10-22 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedAircall / shared-contact REST API list/create/update and contact webhooks; customer-private Basic authentication and approved partner OAuth have distinct eligibility. Call content and recordings are excluded. External code can use the scoped API; native workflow portability is not established. | Aircall customer and partner authentication ↗Application authenticationChecked 2026-10-22 |
| What rights or portability are documented for custom workflow artifacts? | -Aircall / shared-contact REST API list/create/update and contact webhooks; customer-private Basic authentication and approved partner OAuth have distinct eligibility. Call content and recordings are excluded. Native workflow ownership and reusable export rights require a separate contractual review. | Aircall customer and partner authentication ↗Access route; native artifact rights unresolvedChecked 2026-10-22 |
| What permission is needed for the documented downstream use? | -Aircall / shared-contact REST API list/create/update and contact webhooks; customer-private Basic authentication and approved partner OAuth have distinct eligibility. Call content and recordings are excluded. Applicable processing, AI-use and redistribution terms remain unresolved. | Aircall customer and partner authentication ↗Access route; downstream 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 subscription and exact customer or partner API charges
- Completeness of creation-date partitioning at large record volumes
- 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.