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
Paddle Billing API v1 / seller API keys, customers, billing events and notifications; Paddle Classic is excluded.
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
Paddle Billing API v1 / seller API keys, customers, billing events and notifications; Paddle Classic is excluded.
List customers; paginated structured customer collection
List customers ↗
List customers; paginated structured customer collection · Checked 2026-10-16
Query expressiveness 8.8/10
Documented structured API filters
Paddle Billing API v1 / seller API keys, customers, billing events and notifications; Paddle Classic is excluded.
Event type, ordering, after and per_page parameters
List events ↗
Event type, ordering, after and per_page parameters · Checked 2026-10-16
Access cost barrier -
-
Paddle Billing API v1 / seller API keys, customers, billing events and notifications; Paddle Classic is excluded.
Reviewed entitlement documentation; minimum eligible plan and fixed route-specific access charges remain unresolved
API 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 -
-
Paddle Billing API v1 / seller API keys, customers, billing events and notifications; Paddle Classic is excluded.
Seller API-key permissions documented; chosen-third-party enrollment conditions unresolved
API Authentication ↗
Seller API-key permissions documented; chosen-third-party enrollment conditions unresolved · Checked 2026-10-16
Downstream permission -
-
Paddle Billing API v1 / seller API keys, customers, billing events and notifications; Paddle Classic is excluded.
Reviewed access documentation; applicable downstream processing, AI and redistribution terms not established
API 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
Paddle Billing API v1 / seller API keys, customers, billing events and notifications; Paddle Classic is excluded.
POST /customers with customer.write permission
Create a customer ↗
POST /customers with customer.write permission · Checked 2026-10-16
Custom application path -
-
Paddle Billing API v1 / seller API keys, customers, billing events and notifications; Paddle Classic is excluded.
Current chosen-application distribution and approval conditions remain unresolved
API 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
Paddle Billing API v1 / seller API keys, customers, billing events and notifications; Paddle Classic is excluded.
Paginated billing event stream
List events ↗
Paginated billing event stream · Checked 2026-10-16
Limit visibility 10.0/10
Published numeric quotas and recovery instructions
Paddle Billing API v1 / seller API keys, customers, billing events and notifications; Paddle Classic is excluded.
240 requests/minute/IP for most endpoints; 429 and Retry-After; endpoint-specific exceptions
Rate limiting ↗
240 requests/minute/IP for most endpoints; 429 and Retry-After; endpoint-specific exceptions · Checked 2026-10-16
CDC and deletion capture -
-
Paddle Billing API v1 / seller API keys, customers, billing events and notifications; Paddle Classic is excluded.
Event stream existence does not establish all customer/billing deletion identities
List events ↗
Event stream existence does not establish all customer/billing deletion identities · Checked 2026-10-16
Replay and gap recovery 7.5/10
Replay/change queries within a documented retention window
Paddle Billing API v1 / seller API keys, customers, billing events and notifications; Paddle Classic is excluded.
90-day event retention; older events unavailable; replay requires bounded backfill or fresh snapshot
List events ↗
90-day event retention; older events unavailable; replay requires bounded backfill or fresh snapshot · 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
Paddle Billing API v1 / seller API keys, customers, billing events and notifications; Paddle Classic is excluded.
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.
Paddle Billing API v1 / seller API keys, customers, billing events and notifications; Paddle Classic is excluded.
Applicable post-cancellation retrieval clause not established by reviewed technical documentation
API 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
Paddle Billing API v1 / seller API keys, customers, billing events and notifications; Paddle Classic is excluded.
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
Paddle Billing API v1 / seller API keys, customers, billing events and notifications; Paddle Classic is excluded.
Customer integration code can run outside the provider; native workflow authoring not established
API Authentication ↗
Customer integration code can run outside the provider; native workflow authoring not established · Checked 2026-10-16
Rights to custom logic -
-
Paddle Billing API v1 / seller API keys, customers, billing events and notifications; Paddle Classic is excluded.
Ownership and reusable export or independent execution of native workflow artifacts remain unresolved
API 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
Seller API keys carry permissions such as customer.write and notification.read. Customer authorization, third-party public app distribution and seller account approval remain distinct; the latter distribution conditions were not fully established here.
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
The API uses paginated lists and customer records with created/updated timestamps. Events are ordered by event ID and support paging; events older than 90 days are not retained.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| Paddle scoped API access | API key | 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
Current minimum seller entitlement and fixed access fees remain unresolved in the reviewed technical pages. Transaction processing charges are not assumed to prove the absence of a fixed API access fee.
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 /customers with customer.write. Creating a customer does not authorize payments or a subscription charge; those actions require separate endpoints and approval.
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
Webhooks signal supported billing events, and the event API exposes the last 90 days for polling after gaps. Most API operations permit 240 requests per minute per IP, with numeric exceptions and Retry-After handling.
CDC, deletions and recovery
| Question | Answer / applicable route | Evidence |
|---|---|---|
| Can ongoing extraction identify updates and deleted records on the declared route? | -Paddle Billing API v1 / seller API keys, customers, billing events and notifications; Paddle Classic is excluded. Event stream existence does not establish all customer/billing deletion identities | List events ↗Event stream existence does not establish all customer/billing deletion identitiesChecked 2026-10-16 |
| How can extraction recover after missed events or an interrupted consumer? | Replay/change queries within a documented retention windowPaddle Billing API v1 / seller API keys, customers, billing events and notifications; Paddle Classic is excluded. 90-day event retention; older events unavailable; replay requires bounded backfill or fresh snapshot | List events ↗90-day event retention; older events unavailable; replay requires bounded backfill or fresh snapshotChecked 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 and retained events can be copied before cancellation. Payment credentials, native checkout configuration and older event history require separate recovery checks; cancellation retrieval rights remain unresolved.
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 applications can implement customer billing rules around fixed APIs. Native workflow ownership and execution elsewhere remain unresolved (a 90-day event list does not export the billing engine).
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 scopePaddle Billing API v1 / seller API keys, customers, billing events and notifications; Paddle Classic is excluded. 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 requestsPaddle Billing API v1 / seller API keys, customers, billing events and notifications; Paddle Classic is excluded. List customers; paginated structured customer collection | List customers ↗List customers; paginated structured customer collectionChecked 2026-10-16 |
| What queries can a customer issue outside the provider UI? | Documented structured API filtersPaddle Billing API v1 / seller API keys, customers, billing events and notifications; Paddle Classic is excluded. Event type, ordering, after and per_page parameters | List events ↗Event type, ordering, after and per_page parametersChecked 2026-10-16 |
| Who decides whether a chosen third party may connect? | -Paddle Billing API v1 / seller API keys, customers, billing events and notifications; Paddle Classic is excluded. Seller API-key permissions documented; chosen-third-party enrollment conditions unresolved | API Authentication ↗Seller API-key permissions documented; chosen-third-party enrollment conditions unresolvedChecked 2026-10-16 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -Paddle Billing API v1 / seller API keys, customers, billing events and notifications; Paddle Classic is excluded. Reviewed entitlement documentation; minimum eligible plan and fixed route-specific access charges remain unresolved | API 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? | -Paddle Billing API v1 / seller API keys, customers, billing events and notifications; Paddle Classic is excluded. Reviewed access documentation; applicable downstream processing, AI and redistribution terms not established | API 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 domainPaddle Billing API v1 / seller API keys, customers, billing events and notifications; Paddle Classic is excluded. POST /customers with customer.write permission | Create a customer ↗POST /customers with customer.write permissionChecked 2026-10-16 |
| How can customers connect an application they build or choose? | -Paddle Billing API v1 / seller API keys, customers, billing events and notifications; Paddle Classic is excluded. Current chosen-application distribution and approval conditions remain unresolved | API 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 webhooksPaddle Billing API v1 / seller API keys, customers, billing events and notifications; Paddle Classic is excluded. Paginated billing event stream | List events ↗Paginated billing event streamChecked 2026-10-16 |
| How are integration limits disclosed? | Published numeric quotas and recovery instructionsPaddle Billing API v1 / seller API keys, customers, billing events and notifications; Paddle Classic is excluded. 240 requests/minute/IP for most endpoints; 429 and Retry-After; endpoint-specific exceptions | Rate limiting ↗240 requests/minute/IP for most endpoints; 429 and Retry-After; endpoint-specific exceptionsChecked 2026-10-16 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsPaddle Billing API v1 / seller API keys, customers, billing events and notifications; Paddle Classic is excluded. 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? | -Paddle Billing API v1 / seller API keys, customers, billing events and notifications; Paddle Classic is excluded. Applicable post-cancellation retrieval clause not established by reviewed technical documentation | API 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 establishedPaddle Billing API v1 / seller API keys, customers, billing events and notifications; Paddle Classic is excluded. Customer integration code can run outside the provider; native workflow authoring not established | API 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? | -Paddle Billing API v1 / seller API keys, customers, billing events and notifications; Paddle Classic is excluded. Ownership and reusable export or independent execution of native workflow artifacts remain unresolved | API 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 unverifiedPaddle Billing API v1 / seller API keys, customers, billing events and notifications; Paddle Classic is excluded. 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
- Complete declared update and deletion identity coverage
Documentation
Assessment checked 2026-10-16. Each answer retains its source and applicable route; the check date does not establish live account behavior.