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
Payload / configured REST collection records and CRUD using user-bound API keys; database dumps, uploads, globals and full application migration are excluded.
Payload mounts REST collection APIs at each configured collection slug. Access Control and query depth determine visible records and relationships.
Payload REST collection APIs ↗
Collections and REST query parameters · Checked 2026-10-22
Bulk delivery 8.8/10
Batched or iterable API requests
Payload / configured REST collection records and CRUD using user-bound API keys; database dumps, uploads, globals and full application migration are excluded.
Traverse find results with limit and page, retaining docs and pagination metadata. Disabling count calculations does not remove the requested limit.
Payload REST collection APIs ↗
Collections and REST query parameters · Checked 2026-10-22
Payload REST pagination ↗
Options, REST API and Response · Checked 2026-10-22
Query expressiveness 8.8/10
Documented structured API filters
Payload / configured REST collection records and CRUD using user-bound API keys; database dumps, uploads, globals and full application migration are excluded.
REST query parameters select fields, filters, sorting and relationship depth within collection access rules.
Payload REST collection APIs ↗
Collections and REST query parameters · Checked 2026-10-22
Access cost barrier -
-
Payload / configured REST collection records and CRUD using user-bound API keys; database dumps, uploads, globals and full application migration are excluded.
Minimum commercial entitlement and exact API charges were not established for the assessed route.
Payload REST collection APIs ↗
Collections and REST query parameters · Checked 2026-10-22
Third-party accessibility
20% of the overall score before applicability adjustment.
Scored answers and evidence
Third-party eligibility 10.0/10
Customer authorization without discretionary provider approval
Payload / configured REST collection records and CRUD using user-bound API keys; database dumps, uploads, globals and full application migration are excluded.
Enable API-key authentication on an auth collection. Authorization contains the collection slug, API-Key and the key; requests act as the associated user under normal Access Control.
Payload user-bound API-key authentication ↗
HTTP Authentication and uniform Access Control · Checked 2026-10-22
Downstream permission -
-
Payload / configured REST collection records and CRUD using user-bound API keys; database dumps, uploads, globals and full application migration are excluded.
Processing, AI-use, redistribution and other downstream contractual permissions were not settled by this technical review.
Payload user-bound API-key authentication ↗
HTTP Authentication and uniform Access Control · Checked 2026-10-22
External action
15% of the overall score before applicability adjustment.
Scored answers and evidence
Write interface 10.0/10
Customer-configurable write interfaces with validation
Payload / configured REST collection records and CRUD using user-bound API keys; database dumps, uploads, globals and full application migration are excluded.
Configured collections expose create, update and delete REST operations. Custom endpoints remain subject to their own implementation and access checks.
Payload REST collection APIs ↗
Collection operation methods and paths · Checked 2026-10-22
Custom application path 10.0/10
Customer-configurable interfaces for custom applications
Payload / configured REST collection records and CRUD using user-bound API keys; database dumps, uploads, globals and full application migration are excluded.
The documented interface can connect customer application code within its authorization and resource scope.
Payload user-bound API-key authentication ↗
HTTP Authentication and uniform Access Control · Checked 2026-10-22
Continuity
15% of the overall score before applicability adjustment.
Scored answers and evidence
Refresh mechanism 5.0/10
Scheduled feeds or recurring extracts
Payload / configured REST collection records and CRUD using user-bound API keys; database dumps, uploads, globals and full application migration are excluded.
Repeat the assessed collection traversal to reconcile current state. Native change delivery and retained replay were not established in this review.
Payload REST collection APIs ↗
Collections and REST query parameters · Checked 2026-10-22
Limit visibility -
-
Payload / configured REST collection records and CRUD using user-bound API keys; database dumps, uploads, globals and full application migration are excluded.
A numeric request budget and recovery contract were not established by the reviewed references.
Payload REST collection APIs ↗
Collections and REST query parameters · Checked 2026-10-22
CDC and deletion capture 2.5/10
Full snapshots permit customer reconciliation; native deltas unverified
Payload / configured REST collection records and CRUD using user-bound API keys; database dumps, uploads, globals and full application migration are excluded.
Compare complete scoped snapshots to reconcile missing records; native deletion identities and intermediate changes were not established.
Payload REST collection APIs ↗
Collections and REST query parameters · Checked 2026-10-22
Replay and gap recovery 2.5/10
Rebuild from a fresh snapshot; no historical replay established
Payload / configured REST collection records and CRUD using user-bound API keys; database dumps, uploads, globals and full application 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.
Payload REST collection APIs ↗
Collections and REST query parameters · 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
Payload / configured REST collection records and CRUD using user-bound API keys; database dumps, uploads, globals and full application migration are excluded.
The assessed structured payloads can be retained in customer-held files. Broader contractual reuse rights remain unresolved.
Payload REST collection APIs ↗
Collections and REST query parameters · Checked 2026-10-22
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
Payload / configured REST collection records and CRUD using user-bound API keys; database dumps, uploads, globals and full application migration are excluded.
The reviewed technical documentation does not establish retrieval rights after account termination.
Payload user-bound API-key authentication ↗
HTTP Authentication and uniform Access Control · Checked 2026-10-22
Planned migration fidelity 7.5/10
Portable structured records on documented routes; whole-product completeness unverified
Payload / configured REST collection records and CRUD using user-bound API keys; database dumps, uploads, globals and full application migration are excluded.
Retain the assessed structured records before losing access. Attachments, historical versions, permissions and full product configuration need separate extraction.
Payload REST collection APIs ↗
Collections and REST query parameters · 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
Payload / configured REST collection records and CRUD using user-bound API keys; database dumps, uploads, globals and full application migration are excluded.
External code can use this interface; native workflow portability was not established (API clients and native definitions are different artifacts).
Payload user-bound API-key authentication ↗
HTTP Authentication and uniform Access Control · Checked 2026-10-22
Rights to custom logic -
-
Payload / configured REST collection records and CRUD using user-bound API keys; database dumps, uploads, globals and full application migration are excluded.
Ownership and reusable export rights for native workflow artifacts need a separate contractual review.
Payload user-bound API-key authentication ↗
HTTP Authentication and uniform Access Control · 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
Enable API-key authentication on an auth collection. Authorization contains the collection slug, API-Key and the key; requests act as the associated user under normal Access Control.
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 find results with limit and page, retaining docs and pagination metadata. Disabling count calculations does not remove the requested limit. REST query parameters select fields, filters, sorting and relationship depth within collection access rules.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| configured REST collection records and CRUD using user-bound API keys | 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
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
Configured collections expose create, update and delete REST operations. Custom endpoints remain subject to their own implementation and access checks.
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
Repeat the assessed collection traversal to reconcile current state. Native change delivery and retained replay were not established in this review.
CDC, deletions and recovery
| Question | Answer / applicable route | Evidence |
|---|---|---|
| Can ongoing extraction identify updates and deleted records on the declared route? | Full snapshots permit customer reconciliation; native deltas unverifiedPayload / configured REST collection records and CRUD using user-bound API keys; database dumps, uploads, globals and full application migration are excluded. Compare complete scoped snapshots to reconcile missing records; native deletion identities and intermediate changes were not established. | Payload REST collection APIs ↗Collections and REST query parametersChecked 2026-10-22 |
| How can extraction recover after missed events or an interrupted consumer? | Rebuild from a fresh snapshot; no historical replay establishedPayload / configured REST collection records and CRUD using user-bound API keys; database dumps, uploads, globals and full application 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. | Payload REST collection APIs ↗Collections and REST query parametersChecked 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 scopePayload / configured REST collection records and CRUD using user-bound API keys; database dumps, uploads, globals and full application migration are excluded. Payload mounts REST collection APIs at each configured collection slug. Access Control and query depth determine visible records and relationships. | Payload REST collection APIs ↗Collections and REST query parametersChecked 2026-10-22 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsPayload / configured REST collection records and CRUD using user-bound API keys; database dumps, uploads, globals and full application migration are excluded. Traverse find results with limit and page, retaining docs and pagination metadata. Disabling count calculations does not remove the requested limit. | Payload REST collection APIs ↗Collections and REST query parametersChecked 2026-10-22 Payload REST pagination ↗Options, REST API and ResponseChecked 2026-10-22 |
| What queries can a customer issue outside the provider UI? | Documented structured API filtersPayload / configured REST collection records and CRUD using user-bound API keys; database dumps, uploads, globals and full application migration are excluded. REST query parameters select fields, filters, sorting and relationship depth within collection access rules. | Payload REST collection APIs ↗Collections and REST query parametersChecked 2026-10-22 |
| Who decides whether a chosen third party may connect? | Customer authorization without discretionary provider approvalPayload / configured REST collection records and CRUD using user-bound API keys; database dumps, uploads, globals and full application migration are excluded. Enable API-key authentication on an auth collection. Authorization contains the collection slug, API-Key and the key; requests act as the associated user under normal Access Control. | Payload user-bound API-key authentication ↗HTTP Authentication and uniform Access ControlChecked 2026-10-22 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -Payload / configured REST collection records and CRUD using user-bound API keys; database dumps, uploads, globals and full application migration are excluded. Minimum commercial entitlement and exact API charges were not established for the assessed route. | Payload REST collection APIs ↗Collections and REST query parametersChecked 2026-10-22 |
| Which external write operations are documented? | Customer-configurable write interfaces with validationPayload / configured REST collection records and CRUD using user-bound API keys; database dumps, uploads, globals and full application migration are excluded. Configured collections expose create, update and delete REST operations. Custom endpoints remain subject to their own implementation and access checks. | Payload REST collection APIs ↗Collection operation methods and pathsChecked 2026-10-22 |
| How can customers connect an application they build or choose? | Customer-configurable interfaces for custom applicationsPayload / configured REST collection records and CRUD using user-bound API keys; database dumps, uploads, globals and full application migration are excluded. The documented interface can connect customer application code within its authorization and resource scope. | Payload user-bound API-key authentication ↗HTTP Authentication and uniform Access ControlChecked 2026-10-22 |
| What mechanism supports repeatable extraction of changes? | Scheduled feeds or recurring extractsPayload / configured REST collection records and CRUD using user-bound API keys; database dumps, uploads, globals and full application migration are excluded. Repeat the assessed collection traversal to reconcile current state. Native change delivery and retained replay were not established in this review. | Payload REST collection APIs ↗Collections and REST query parametersChecked 2026-10-22 |
| How are integration limits disclosed? | -Payload / configured REST collection records and CRUD using user-bound API keys; database dumps, uploads, globals and full application migration are excluded. A numeric request budget and recovery contract were not established by the reviewed references. | Payload REST collection APIs ↗Collections and REST query parametersChecked 2026-10-22 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsPayload / configured REST collection records and CRUD using user-bound API keys; database dumps, uploads, globals and full application migration are excluded. The assessed structured payloads can be retained in customer-held files. Broader contractual reuse rights remain unresolved. | Payload REST collection APIs ↗Collections and REST query parametersChecked 2026-10-22 |
| What retrieval rights are documented at cancellation? | -Payload / configured REST collection records and CRUD using user-bound API keys; database dumps, uploads, globals and full application migration are excluded. The reviewed technical documentation does not establish retrieval rights after account termination. | Payload user-bound API-key authentication ↗HTTP Authentication and uniform Access ControlChecked 2026-10-22 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedPayload / configured REST collection records and CRUD using user-bound API keys; database dumps, uploads, globals and full application migration are excluded. External code can use this interface; native workflow portability was not established (API clients and native definitions are different artifacts). | Payload user-bound API-key authentication ↗HTTP Authentication and uniform Access ControlChecked 2026-10-22 |
| What rights or portability are documented for custom workflow artifacts? | -Payload / configured REST collection records and CRUD using user-bound API keys; database dumps, uploads, globals and full application migration are excluded. Ownership and reusable export rights for native workflow artifacts need a separate contractual review. | Payload user-bound API-key authentication ↗HTTP Authentication and uniform Access ControlChecked 2026-10-22 |
| What usable data or native definitions can leave before cancellation? | Portable structured records on documented routes; whole-product completeness unverifiedPayload / configured REST collection records and CRUD using user-bound API keys; database dumps, uploads, globals and full application migration are excluded. Retain the assessed structured records before losing access. Attachments, historical versions, permissions and full product configuration need separate extraction. | Payload REST collection APIs ↗Collections and REST query parametersChecked 2026-10-22 |
| What permission is needed for the documented downstream use? | -Payload / configured REST collection records and CRUD using user-bound API keys; database dumps, uploads, globals and full application migration are excluded. Processing, AI-use, redistribution and other downstream contractual permissions were not settled by this technical review. | Payload user-bound API-key authentication ↗HTTP Authentication and uniform Access ControlChecked 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.