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
Chargebee Billing API v2 / site-scoped customers and customer lifecycle events; Product Catalog version and business-entity boundaries remain explicit.
Structured read interface for the declared product and resources
List customers ↗
Structured read interface for the declared product and resources · Checked 2026-10-16
Bulk delivery 8.8/10
Batched or iterable API requests
Chargebee Billing API v2 / site-scoped customers and customer lifecycle events; Product Catalog version and business-entity boundaries remain explicit.
Documented list/collection retrieval within the stated endpoint scope; whole-product recovery unverified
List customers ↗
Documented list/collection retrieval within the stated endpoint scope; whole-product recovery unverified · Checked 2026-10-16
Query expressiveness 8.8/10
Documented structured API filters
Chargebee Billing API v2 / site-scoped customers and customer lifecycle events; Product Catalog version and business-entity boundaries remain explicit.
Customer list filters and pagination; eventually consistent
List customers ↗
Customer list filters and pagination; eventually consistent · Checked 2026-10-16
Access cost barrier -
-
Chargebee Billing API v2 / site-scoped customers and customer lifecycle events; Product Catalog version and business-entity boundaries remain explicit.
Reviewed entitlement documentation; minimum eligible plan and fixed route-specific access charges remain unresolved
Authentication ↗
Reviewed entitlement documentation; minimum eligible plan and fixed route-specific access charges remain unresolved · Checked 2026-10-16
Third-party accessibility
20% of the overall score before applicability adjustment.
Scored answers and evidence
Third-party eligibility -
-
Chargebee Billing API v2 / site-scoped customers and customer lifecycle events; Product Catalog version and business-entity boundaries remain explicit.
Site-key authentication reviewed; full chosen-third-party distribution terms unresolved
Authentication ↗
Site-key authentication reviewed; full chosen-third-party distribution terms unresolved · Checked 2026-10-16
Downstream permission -
-
Chargebee Billing API v2 / site-scoped customers and customer lifecycle events; Product Catalog version and business-entity boundaries remain explicit.
Reviewed access documentation; applicable downstream processing, AI and redistribution terms not established
Authentication ↗
Reviewed access documentation; applicable downstream processing, AI and redistribution terms not established · Checked 2026-10-16
External action
15% of the overall score before applicability adjustment.
Scored answers and evidence
Write interface 2.5/10
Named operations in a limited domain
Chargebee Billing API v2 / site-scoped customers and customer lifecycle events; Product Catalog version and business-entity boundaries remain explicit.
POST /api/v2/customers; Idempotency Supported
Create a customer ↗
POST /api/v2/customers; Idempotency Supported · Checked 2026-10-16
Custom application path -
-
Chargebee Billing API v2 / site-scoped customers and customer lifecycle events; Product Catalog version and business-entity boundaries remain explicit.
Current chosen-application distribution and approval conditions remain unresolved
Authentication ↗
Current chosen-application distribution and approval conditions remain unresolved · 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
Chargebee Billing API v2 / site-scoped customers and customer lifecycle events; Product Catalog version and business-entity boundaries remain explicit.
Event list filters and webhook notifications
List events ↗
Event list filters and webhook notifications · Checked 2026-10-16
Limit visibility -
-
Chargebee Billing API v2 / site-scoped customers and customer lifecycle events; Product Catalog version and business-entity boundaries remain explicit.
Route-specific numeric throughput and recovery conditions remain unresolved
Authentication ↗
Route-specific numeric throughput and recovery conditions remain unresolved · Checked 2026-10-16
CDC and deletion capture 7.5/10
Updates and deletion identities documented for the stated resources
Chargebee Billing API v2 / site-scoped customers and customer lifecycle events; Product Catalog version and business-entity boundaries remain explicit.
Customer create/change/delete event types with event/resource identities
List events ↗
Customer create/change/delete event types with event/resource identities · Checked 2026-10-16
Replay and gap recovery 5.0/10
Bounded redelivery or overlapping queries; no durable consumer checkpoint
Chargebee Billing API v2 / site-scoped customers and customer lifecycle events; Product Catalog version and business-entity boundaries remain explicit.
Webhook retry and manual resend; conflicting retry-duration text and retained event window unresolved
Events and webhook handling ↗
Webhook retry and manual resend; conflicting retry-duration text and retained event window unresolved · 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
Chargebee Billing API v2 / site-scoped customers and customer lifecycle events; Product Catalog version and business-entity boundaries remain explicit.
Customer-held structured API records within the declared resource scope
List customers ↗
Customer-held structured API records within the declared resource scope · Checked 2026-10-16
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
Chargebee Billing API v2 / site-scoped customers and customer lifecycle events; Product Catalog version and business-entity boundaries remain explicit.
Applicable post-cancellation retrieval clause not established by reviewed technical documentation
Authentication ↗
Applicable post-cancellation retrieval clause not established by reviewed technical documentation · Checked 2026-10-16
Planned migration fidelity 7.5/10
Portable structured records on documented routes; whole-product completeness unverified
Chargebee Billing API v2 / site-scoped customers and customer lifecycle events; Product Catalog version and business-entity boundaries remain explicit.
Structured resource records can be retrieved; complete attachments, versions, relationships and native configuration remain unverified
List customers ↗
Structured resource records can be retrieved; complete attachments, versions, relationships and native configuration remain unverified · 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
Chargebee Billing API v2 / site-scoped customers and customer lifecycle events; Product Catalog version and business-entity boundaries remain explicit.
Customer integration code can run outside the provider; native workflow authoring not established
Authentication ↗
Customer integration code can run outside the provider; native workflow authoring not established · Checked 2026-10-16
Rights to custom logic -
-
Chargebee Billing API v2 / site-scoped customers and customer lifecycle events; Product Catalog version and business-entity boundaries remain explicit.
Ownership and reusable export or independent execution of native workflow artifacts remain unresolved
Authentication ↗
Ownership and reusable export or independent execution of native workflow artifacts remain unresolved · 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
Server requests authenticate with site API keys through HTTP Basic. Customer keys and public partner distribution are different arrangements; the reviewed authentication page does not establish a chosen third party’s complete enrollment contract.
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
Customer lists accept filters and are marked eventually consistent. Customer IDs can change during business-entity transfers, so identity mapping needs more than assuming IDs never move. Customer exports are a separate API route.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| Chargebee scoped API access | HTTP Basic | Customer | Not confirmed | Not confirmed | 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 reviewed authentication and resource references do not establish the minimum plan or any fixed access fee. Production request limits need the site’s applicable plan and quota contract.
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 Customer documents POST /api/v2/customers and marks idempotency as supported. Payment-source creation is a separate operation recommended by Chargebee to isolate gateway failures from customer creation.
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
Events include customer_created, customer_changed and customer_deleted. resource_version can order updates, while event IDs identify duplicate delivery. Retry documentation contains differing timing descriptions, so this review credits bounded retries without adopting a single retention duration.
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 resourcesChargebee Billing API v2 / site-scoped customers and customer lifecycle events; Product Catalog version and business-entity boundaries remain explicit. Customer create/change/delete event types with event/resource identities | List events ↗Customer create/change/delete event types with event/resource identitiesChecked 2026-10-16 |
| How can extraction recover after missed events or an interrupted consumer? | Bounded redelivery or overlapping queries; no durable consumer checkpointChargebee Billing API v2 / site-scoped customers and customer lifecycle events; Product Catalog version and business-entity boundaries remain explicit. Webhook retry and manual resend; conflicting retry-duration text and retained event window unresolved | Events and webhook handling ↗Webhook retry and manual resend; conflicting retry-duration text and retained event window unresolvedChecked 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
Customer records can be held externally before cancellation. Payment vault contents, complete historical versions and native billing configuration require separate recovery evidence; customer-record export is not a portable payment processor.
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
External integrations can reconcile customer changes and run customer rules. Native billing-workflow ownership and independent execution remain unresolved (a resource version is not an exportable pricing definition).
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 scopeChargebee Billing API v2 / site-scoped customers and customer lifecycle events; Product Catalog version and business-entity boundaries remain explicit. Structured read interface for the declared product and resources | List customers ↗Structured read interface for the declared product and resourcesChecked 2026-10-16 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsChargebee Billing API v2 / site-scoped customers and customer lifecycle events; Product Catalog version and business-entity boundaries remain explicit. Documented list/collection retrieval within the stated endpoint scope; whole-product recovery unverified | List customers ↗Documented list/collection retrieval within the stated endpoint scope; whole-product recovery unverifiedChecked 2026-10-16 |
| What queries can a customer issue outside the provider UI? | Documented structured API filtersChargebee Billing API v2 / site-scoped customers and customer lifecycle events; Product Catalog version and business-entity boundaries remain explicit. Customer list filters and pagination; eventually consistent | List customers ↗Customer list filters and pagination; eventually consistentChecked 2026-10-16 |
| Who decides whether a chosen third party may connect? | -Chargebee Billing API v2 / site-scoped customers and customer lifecycle events; Product Catalog version and business-entity boundaries remain explicit. Site-key authentication reviewed; full chosen-third-party distribution terms unresolved | Authentication ↗Site-key authentication reviewed; full chosen-third-party distribution terms unresolvedChecked 2026-10-16 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -Chargebee Billing API v2 / site-scoped customers and customer lifecycle events; Product Catalog version and business-entity boundaries remain explicit. Reviewed entitlement documentation; minimum eligible plan and fixed route-specific access charges remain unresolved | Authentication ↗Reviewed entitlement documentation; minimum eligible plan and fixed route-specific access charges remain unresolvedChecked 2026-10-16 |
| What permission is needed for the documented downstream use? | -Chargebee Billing API v2 / site-scoped customers and customer lifecycle events; Product Catalog version and business-entity boundaries remain explicit. Reviewed access documentation; applicable downstream processing, AI and redistribution terms not established | Authentication ↗Reviewed access documentation; applicable downstream processing, AI and redistribution terms not establishedChecked 2026-10-16 |
| Which external write operations are documented? | Named operations in a limited domainChargebee Billing API v2 / site-scoped customers and customer lifecycle events; Product Catalog version and business-entity boundaries remain explicit. POST /api/v2/customers; Idempotency Supported | Create a customer ↗POST /api/v2/customers; Idempotency SupportedChecked 2026-10-16 |
| How can customers connect an application they build or choose? | -Chargebee Billing API v2 / site-scoped customers and customer lifecycle events; Product Catalog version and business-entity boundaries remain explicit. Current chosen-application distribution and approval conditions remain unresolved | Authentication ↗Current chosen-application distribution and approval conditions remain unresolvedChecked 2026-10-16 |
| What mechanism supports repeatable extraction of changes? | Documented updated-since filters or webhooksChargebee Billing API v2 / site-scoped customers and customer lifecycle events; Product Catalog version and business-entity boundaries remain explicit. Event list filters and webhook notifications | List events ↗Event list filters and webhook notificationsChecked 2026-10-16 |
| How are integration limits disclosed? | -Chargebee Billing API v2 / site-scoped customers and customer lifecycle events; Product Catalog version and business-entity boundaries remain explicit. Route-specific numeric throughput and recovery conditions remain unresolved | Authentication ↗Route-specific numeric throughput and recovery conditions remain unresolvedChecked 2026-10-16 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsChargebee Billing API v2 / site-scoped customers and customer lifecycle events; Product Catalog version and business-entity boundaries remain explicit. Customer-held structured API records within the declared resource scope | List customers ↗Customer-held structured API records within the declared resource scopeChecked 2026-10-16 |
| What retrieval rights are documented at cancellation? | -Chargebee Billing API v2 / site-scoped customers and customer lifecycle events; Product Catalog version and business-entity boundaries remain explicit. Applicable post-cancellation retrieval clause not established by reviewed technical documentation | Authentication ↗Applicable post-cancellation retrieval clause not established by reviewed technical documentationChecked 2026-10-16 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedChargebee Billing API v2 / site-scoped customers and customer lifecycle events; Product Catalog version and business-entity boundaries remain explicit. Customer integration code can run outside the provider; native workflow authoring not established | Authentication ↗Customer integration code can run outside the provider; native workflow authoring not establishedChecked 2026-10-16 |
| What rights or portability are documented for custom workflow artifacts? | -Chargebee Billing API v2 / site-scoped customers and customer lifecycle events; Product Catalog version and business-entity boundaries remain explicit. Ownership and reusable export or independent execution of native workflow artifacts remain unresolved | Authentication ↗Ownership and reusable export or independent execution of native workflow artifacts remain unresolvedChecked 2026-10-16 |
| What usable data or native definitions can leave before cancellation? | Portable structured records on documented routes; whole-product completeness unverifiedChargebee Billing API v2 / site-scoped customers and customer lifecycle events; Product Catalog version and business-entity boundaries remain explicit. Structured resource records can be retrieved; complete attachments, versions, relationships and native configuration remain unverified | List customers ↗Structured resource records can be retrieved; complete attachments, versions, relationships and native configuration remain unverifiedChecked 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 eligible plan and fixed API access fees
- Applicable downstream-use and customer cancellation terms
- Complete file, history and configuration recovery
- Native workflow artifact ownership and independent execution
Documentation
Assessment checked 2026-10-16. Each answer retains its source and applicable route; the check date does not establish live account behavior.