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
Kit / v4 OAuth subscriber enumeration and subscriber creation; email content, automations, purchase APIs and complete account migration are excluded.
Kit v4 returns subscriber records with status and optional fields. Results are eventually consistent and can lag recent changes.
Kit v4 subscriber listing ↗
Pagination, status, updated_after, slim and eventual consistency · Checked 2026-10-22
Bulk delivery 8.8/10
Batched or iterable API requests
Kit / v4 OAuth subscriber enumeration and subscriber creation; email content, automations, purchase APIs and complete account migration are excluded.
Traverse the subscriber collection’s before/after cursors and pagination metadata; include all required statuses explicitly.
Kit v4 subscriber listing ↗
Pagination, status, updated_after, slim and eventual consistency · Checked 2026-10-22
Query expressiveness 8.8/10
Documented structured API filters
Kit / v4 OAuth subscriber enumeration and subscriber creation; email content, automations, purchase APIs and complete account migration are excluded.
created_after/before and updated_after/before select dates. slim=true omits custom fields, so avoid it for a fuller record copy.
Kit v4 subscriber listing ↗
Pagination, status, updated_after, slim and eventual consistency · Checked 2026-10-22
Access cost barrier -
-
Kit / v4 OAuth subscriber enumeration and subscriber creation; email content, automations, purchase APIs and complete account migration are excluded.
Minimum commercial entitlement and exact API charges were not established for the assessed route.
Kit v4 subscriber listing ↗
Pagination, status, updated_after, slim and eventual consistency · Checked 2026-10-22
Third-party accessibility
20% of the overall score before applicability adjustment.
Scored answers and evidence
Third-party eligibility -
-
Kit / v4 OAuth subscriber enumeration and subscriber creation; email content, automations, purchase APIs and complete account migration are excluded.
The technical route is documented; eligibility and review for independently distributed third-party applications remain unresolved.
Kit app OAuth and API-key boundary ↗
API keys and Creating and configuring your OAuth powered app · Checked 2026-10-22
Downstream permission -
-
Kit / v4 OAuth subscriber enumeration and subscriber creation; email content, automations, purchase APIs and complete account migration are excluded.
Processing, AI-use, redistribution and other downstream contractual permissions were not settled by this technical review.
Kit app OAuth and API-key boundary ↗
API keys and Creating and configuring your OAuth powered app · 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
Kit / v4 OAuth subscriber enumeration and subscriber creation; email content, automations, purchase APIs and complete account migration are excluded.
Create subscribers through the v4 create-subscriber operation with the supported OAuth grant.
Kit v4 create subscriber ↗
Create a subscriber · Checked 2026-10-22
Custom application path 10.0/10
Customer applications using fixed APIs without provider selection
Kit / v4 OAuth subscriber enumeration and subscriber creation; email content, automations, purchase APIs and complete account migration are excluded.
The documented interface can connect customer application code within its authorization and resource scope.
Kit app OAuth and API-key boundary ↗
API keys and Creating and configuring your OAuth powered app · 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
Kit / v4 OAuth subscriber enumeration and subscriber creation; email content, automations, purchase APIs and complete account migration are excluded.
updated_after and updated_before support incremental subscriber reads. Eventual consistency requires overlap; deletion capture remains unresolved.
Kit v4 subscriber listing ↗
Pagination, status, updated_after, slim and eventual consistency · Checked 2026-10-22
Limit visibility 7.5/10
Numeric usage or polling guidance
Kit / v4 OAuth subscriber enumeration and subscriber creation; email content, automations, purchase APIs and complete account migration are excluded.
API keys allow 120 requests per rolling 60 seconds; OAuth allows 600. Some bulk endpoints require OAuth.
Kit app OAuth and API-key boundary ↗
API-key restrictions and OAuth allowance · Checked 2026-10-22
CDC and deletion capture 5.0/10
Updates identified; deletion capture not established
Kit / v4 OAuth subscriber enumeration and subscriber creation; email content, automations, purchase APIs and complete account migration are excluded.
Updated-date filters expose changed current subscribers; unsubscribe state differs from permanent record deletion.
Kit v4 subscriber listing ↗
Pagination, status, updated_after, slim and eventual consistency · Checked 2026-10-22
Replay and gap recovery 2.5/10
Rebuild from a fresh snapshot; no historical replay established
Kit / v4 OAuth subscriber enumeration and subscriber creation; email content, automations, purchase APIs and complete account migration are excluded.
Repeat the declared collection or export route to rebuild current state within its permissions and selection limits. Deleted payloads and intermediate history are unverified.
Kit v4 subscriber listing ↗
Pagination, status, updated_after, slim and eventual consistency · 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
Kit / v4 OAuth subscriber enumeration and subscriber creation; email content, automations, purchase APIs and complete account migration are excluded.
The assessed structured payloads can be retained in customer-held files. Broader contractual reuse rights remain unresolved.
Kit v4 subscriber listing ↗
Pagination, status, updated_after, slim and eventual consistency · Checked 2026-10-22
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
Kit / v4 OAuth subscriber enumeration and subscriber creation; email content, automations, purchase APIs and complete account migration are excluded.
The reviewed technical documentation does not establish retrieval rights after account termination.
Kit app OAuth and API-key boundary ↗
API keys and Creating and configuring your OAuth powered app · Checked 2026-10-22
Planned migration fidelity 7.5/10
Portable structured records on documented routes; whole-product completeness unverified
Kit / v4 OAuth subscriber enumeration and subscriber creation; email content, automations, purchase APIs and complete account migration are excluded.
Retain the assessed structured records before losing access. Attachments, historical versions, permissions and full product configuration need separate extraction.
Kit v4 subscriber listing ↗
Pagination, status, updated_after, slim and eventual consistency · 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
Kit / v4 OAuth subscriber enumeration and subscriber creation; email content, automations, purchase APIs and complete account migration are excluded.
External code can use this interface; native workflow portability was not established (API clients and native definitions are different artifacts).
Kit app OAuth and API-key boundary ↗
API keys and Creating and configuring your OAuth powered app · Checked 2026-10-22
Rights to custom logic -
-
Kit / v4 OAuth subscriber enumeration and subscriber creation; email content, automations, purchase APIs and complete account migration are excluded.
Ownership and reusable export rights for native workflow artifacts need a separate contractual review.
Kit app OAuth and API-key boundary ↗
API keys and Creating and configuring your OAuth powered app · 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
Apps and public integrations must use OAuth. API keys are for an owner’s account automation and do not receive official support for public integrations.
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 the subscriber collection’s before/after cursors and pagination metadata; include all required statuses explicitly. created_after/before and updated_after/before select dates. slim=true omits custom fields, so avoid it for a fuller record copy.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| v4 OAuth subscriber enumeration and subscriber creation | oauth2 | partner | Not confirmed | Not confirmed | 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
Minimum plan and exact route fees 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 subscribers through the v4 create-subscriber operation with the supported OAuth grant.
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
updated_after and updated_before support incremental subscriber reads. Eventual consistency requires overlap; deletion capture remains unresolved.
CDC, deletions and recovery
| Question | Answer / applicable route | Evidence |
|---|---|---|
| Can ongoing extraction identify updates and deleted records on the declared route? | Updates identified; deletion capture not establishedKit / v4 OAuth subscriber enumeration and subscriber creation; email content, automations, purchase APIs and complete account migration are excluded. Updated-date filters expose changed current subscribers; unsubscribe state differs from permanent record deletion. | Kit v4 subscriber listing ↗Pagination, status, updated_after, slim and eventual consistencyChecked 2026-10-22 |
| How can extraction recover after missed events or an interrupted consumer? | Rebuild from a fresh snapshot; no historical replay establishedKit / v4 OAuth subscriber enumeration and subscriber creation; email content, automations, purchase APIs and complete account migration are excluded. Repeat the declared collection or export route to rebuild current state within its permissions and selection limits. Deleted payloads and intermediate history are unverified. | Kit v4 subscriber listing ↗Pagination, status, updated_after, slim and eventual consistencyChecked 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
Retain the assessed structured records before losing access. Attachments, historical versions, permissions and full product configuration need 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. Native workflow rights and independent execution remain unresolved (record access does not establish portable application 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 scopeKit / v4 OAuth subscriber enumeration and subscriber creation; email content, automations, purchase APIs and complete account migration are excluded. Kit v4 returns subscriber records with status and optional fields. Results are eventually consistent and can lag recent changes. | Kit v4 subscriber listing ↗Pagination, status, updated_after, slim and eventual consistencyChecked 2026-10-22 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsKit / v4 OAuth subscriber enumeration and subscriber creation; email content, automations, purchase APIs and complete account migration are excluded. Traverse the subscriber collection’s before/after cursors and pagination metadata; include all required statuses explicitly. | Kit v4 subscriber listing ↗Pagination, status, updated_after, slim and eventual consistencyChecked 2026-10-22 |
| What queries can a customer issue outside the provider UI? | Documented structured API filtersKit / v4 OAuth subscriber enumeration and subscriber creation; email content, automations, purchase APIs and complete account migration are excluded. created_after/before and updated_after/before select dates. slim=true omits custom fields, so avoid it for a fuller record copy. | Kit v4 subscriber listing ↗Pagination, status, updated_after, slim and eventual consistencyChecked 2026-10-22 |
| Who decides whether a chosen third party may connect? | -Kit / v4 OAuth subscriber enumeration and subscriber creation; email content, automations, purchase APIs and complete account migration are excluded. The technical route is documented; eligibility and review for independently distributed third-party applications remain unresolved. | Kit app OAuth and API-key boundary ↗API keys and Creating and configuring your OAuth powered appChecked 2026-10-22 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -Kit / v4 OAuth subscriber enumeration and subscriber creation; email content, automations, purchase APIs and complete account migration are excluded. Minimum commercial entitlement and exact API charges were not established for the assessed route. | Kit v4 subscriber listing ↗Pagination, status, updated_after, slim and eventual consistencyChecked 2026-10-22 |
| Which external write operations are documented? | Create and update in one business domainKit / v4 OAuth subscriber enumeration and subscriber creation; email content, automations, purchase APIs and complete account migration are excluded. Create subscribers through the v4 create-subscriber operation with the supported OAuth grant. | Kit v4 create subscriber ↗Create a subscriberChecked 2026-10-22 |
| How can customers connect an application they build or choose? | Customer applications using fixed APIs without provider selectionKit / v4 OAuth subscriber enumeration and subscriber creation; email content, automations, purchase APIs and complete account migration are excluded. The documented interface can connect customer application code within its authorization and resource scope. | Kit app OAuth and API-key boundary ↗API keys and Creating and configuring your OAuth powered appChecked 2026-10-22 |
| What mechanism supports repeatable extraction of changes? | Documented updated-since filters or webhooksKit / v4 OAuth subscriber enumeration and subscriber creation; email content, automations, purchase APIs and complete account migration are excluded. updated_after and updated_before support incremental subscriber reads. Eventual consistency requires overlap; deletion capture remains unresolved. | Kit v4 subscriber listing ↗Pagination, status, updated_after, slim and eventual consistencyChecked 2026-10-22 |
| How are integration limits disclosed? | Numeric usage or polling guidanceKit / v4 OAuth subscriber enumeration and subscriber creation; email content, automations, purchase APIs and complete account migration are excluded. API keys allow 120 requests per rolling 60 seconds; OAuth allows 600. Some bulk endpoints require OAuth. | Kit app OAuth and API-key boundary ↗API-key restrictions and OAuth allowanceChecked 2026-10-22 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsKit / v4 OAuth subscriber enumeration and subscriber creation; email content, automations, purchase APIs and complete account migration are excluded. The assessed structured payloads can be retained in customer-held files. Broader contractual reuse rights remain unresolved. | Kit v4 subscriber listing ↗Pagination, status, updated_after, slim and eventual consistencyChecked 2026-10-22 |
| What retrieval rights are documented at cancellation? | -Kit / v4 OAuth subscriber enumeration and subscriber creation; email content, automations, purchase APIs and complete account migration are excluded. The reviewed technical documentation does not establish retrieval rights after account termination. | Kit app OAuth and API-key boundary ↗API keys and Creating and configuring your OAuth powered appChecked 2026-10-22 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedKit / v4 OAuth subscriber enumeration and subscriber creation; email content, automations, purchase APIs and complete account migration are excluded. External code can use this interface; native workflow portability was not established (API clients and native definitions are different artifacts). | Kit app OAuth and API-key boundary ↗API keys and Creating and configuring your OAuth powered appChecked 2026-10-22 |
| What rights or portability are documented for custom workflow artifacts? | -Kit / v4 OAuth subscriber enumeration and subscriber creation; email content, automations, purchase APIs and complete account migration are excluded. Ownership and reusable export rights for native workflow artifacts need a separate contractual review. | Kit app OAuth and API-key boundary ↗API keys and Creating and configuring your OAuth powered appChecked 2026-10-22 |
| What usable data or native definitions can leave before cancellation? | Portable structured records on documented routes; whole-product completeness unverifiedKit / v4 OAuth subscriber enumeration and subscriber creation; email content, automations, purchase APIs and complete account migration are excluded. Retain the assessed structured records before losing access. Attachments, historical versions, permissions and full product configuration need separate extraction. | Kit v4 subscriber listing ↗Pagination, status, updated_after, slim and eventual consistencyChecked 2026-10-22 |
| What permission is needed for the documented downstream use? | -Kit / v4 OAuth subscriber enumeration and subscriber creation; email content, automations, purchase APIs and complete account migration are excluded. Processing, AI-use, redistribution and other downstream contractual permissions were not settled by this technical review. | Kit app OAuth and API-key boundary ↗API keys and Creating and configuring your OAuth powered appChecked 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 commercial entitlement and exact API charges
- Downstream contractual permissions and post-cancellation retrieval rights
- Complete migration of history, files, permissions and native workflow definitions
Documentation
Assessment checked 2026-10-22. Each answer retains its source and applicable route; the check date does not establish live account behavior.