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
PandaDoc / document-list metadata and template-based document creation via production API keys; signed binaries and complete content-library migration are excluded.
PandaDoc exposes document metadata with lifecycle dates, status and folder filters. Document bodies require separate detail or download routes.
PandaDoc list and search documents ↗
page, count, order_by, created_from and deleted · Checked 2026-10-22
Bulk delivery 8.8/10
Batched or iterable API requests
PandaDoc / document-list metadata and template-based document creation via production API keys; signed binaries and complete content-library migration are excluded.
Increment page through document search, using count up to 100 per page.
PandaDoc list and search documents ↗
page, count, order_by, created_from and deleted · Checked 2026-10-22
Query expressiveness 8.8/10
Documented structured API filters
PandaDoc / document-list metadata and template-based document creation via production API keys; signed binaries and complete content-library migration are excluded.
Filter by creation dates, template, folder or status; deleted=true selects deleted documents.
PandaDoc list and search documents ↗
page, count, order_by, created_from and deleted · Checked 2026-10-22
Access cost barrier -
-
PandaDoc / document-list metadata and template-based document creation via production API keys; signed binaries and complete content-library migration are excluded.
Minimum commercial entitlement and exact API charges were not established for the assessed route.
PandaDoc list and search documents ↗
page, count, order_by, created_from and deleted · Checked 2026-10-22
Third-party accessibility
20% of the overall score before applicability adjustment.
Scored answers and evidence
Third-party eligibility -
-
PandaDoc / document-list metadata and template-based document creation via production API keys; signed binaries and complete content-library migration are excluded.
The technical route is documented; eligibility and review for independently distributed third-party applications remain unresolved.
PandaDoc production API keys ↗
Production API key setup · Checked 2026-10-22
Downstream permission -
-
PandaDoc / document-list metadata and template-based document creation via production API keys; signed binaries and complete content-library migration are excluded.
Processing, AI-use, redistribution and other downstream contractual permissions were not settled by this technical review.
PandaDoc production API keys ↗
Production API key setup · 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
PandaDoc / document-list metadata and template-based document creation via production API keys; signed binaries and complete content-library migration are excluded.
Create documents from templates using the documented creation payload; creation is asynchronous.
PandaDoc create document ↗
Create Document and asynchronous processing · Checked 2026-10-22
Custom application path 10.0/10
Customer applications using fixed APIs without provider selection
PandaDoc / document-list metadata and template-based document creation via production API keys; signed binaries and complete content-library migration are excluded.
The documented interface can connect customer application code within its authorization and resource scope.
PandaDoc production API keys ↗
Production API key setup · 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
PandaDoc / document-list metadata and template-based document creation via production API keys; signed binaries and complete content-library migration are excluded.
Repeat document searches and explicitly include deleted documents. Sorting by date_modified alone is not a durable change stream.
PandaDoc list and search documents ↗
page, count, order_by, created_from and deleted · Checked 2026-10-22
Limit visibility -
-
PandaDoc / document-list metadata and template-based document creation via production API keys; signed binaries and complete content-library migration are excluded.
A numeric request budget and recovery contract were not established by the reviewed references.
PandaDoc list and search documents ↗
page, count, order_by, created_from and deleted · Checked 2026-10-22
CDC and deletion capture 2.5/10
Full snapshots permit customer reconciliation; native deltas unverified
PandaDoc / document-list metadata and template-based document creation via production API keys; signed binaries and complete content-library migration are excluded.
Compare complete scoped snapshots to reconcile missing records; native deletion identities and intermediate changes were not established.
PandaDoc list and search documents ↗
page, count, order_by, created_from and deleted · Checked 2026-10-22
Replay and gap recovery 2.5/10
Rebuild from a fresh snapshot; no historical replay established
PandaDoc / document-list metadata and template-based document creation via production API keys; signed binaries and complete content-library 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.
PandaDoc list and search documents ↗
page, count, order_by, created_from and deleted · 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
PandaDoc / document-list metadata and template-based document creation via production API keys; signed binaries and complete content-library migration are excluded.
The assessed structured payloads can be retained in customer-held files. Broader contractual reuse rights remain unresolved.
PandaDoc list and search documents ↗
page, count, order_by, created_from and deleted · Checked 2026-10-22
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
PandaDoc / document-list metadata and template-based document creation via production API keys; signed binaries and complete content-library migration are excluded.
The reviewed technical documentation does not establish retrieval rights after account termination.
PandaDoc production API keys ↗
Production API key setup · Checked 2026-10-22
Planned migration fidelity 7.5/10
Portable structured records on documented routes; whole-product completeness unverified
PandaDoc / document-list metadata and template-based document creation via production API keys; signed binaries and complete content-library migration are excluded.
Retain the assessed structured records before losing access. Attachments, historical versions, permissions and full product configuration need separate extraction.
PandaDoc list and search documents ↗
page, count, order_by, created_from and deleted · 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
PandaDoc / document-list metadata and template-based document creation via production API keys; signed binaries and complete content-library migration are excluded.
External code can use this interface; native workflow portability was not established (API clients and native definitions are different artifacts).
PandaDoc production API keys ↗
Production API key setup · Checked 2026-10-22
Rights to custom logic -
-
PandaDoc / document-list metadata and template-based document creation via production API keys; signed binaries and complete content-library migration are excluded.
Ownership and reusable export rights for native workflow artifacts need a separate contractual review.
PandaDoc production API keys ↗
Production API key setup · 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
Production API keys are distinct from sandbox keys. Confirm production enablement and commercial entitlement before treating sandbox success as usable access.
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
Increment page through document search, using count up to 100 per page. Filter by creation dates, template, folder or status; deleted=true selects deleted documents.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| document-list metadata and template-based document creation via production API keys | API key | Customer | 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 documents from templates using the documented creation payload; creation is asynchronous.
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 document searches and explicitly include deleted documents. Sorting by date_modified alone is not a durable change stream.
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 unverifiedPandaDoc / document-list metadata and template-based document creation via production API keys; signed binaries and complete content-library migration are excluded. Compare complete scoped snapshots to reconcile missing records; native deletion identities and intermediate changes were not established. | PandaDoc list and search documents ↗page, count, order_by, created_from and deletedChecked 2026-10-22 |
| How can extraction recover after missed events or an interrupted consumer? | Rebuild from a fresh snapshot; no historical replay establishedPandaDoc / document-list metadata and template-based document creation via production API keys; signed binaries and complete content-library 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. | PandaDoc list and search documents ↗page, count, order_by, created_from and deletedChecked 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 scopePandaDoc / document-list metadata and template-based document creation via production API keys; signed binaries and complete content-library migration are excluded. PandaDoc exposes document metadata with lifecycle dates, status and folder filters. Document bodies require separate detail or download routes. | PandaDoc list and search documents ↗page, count, order_by, created_from and deletedChecked 2026-10-22 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsPandaDoc / document-list metadata and template-based document creation via production API keys; signed binaries and complete content-library migration are excluded. Increment page through document search, using count up to 100 per page. | PandaDoc list and search documents ↗page, count, order_by, created_from and deletedChecked 2026-10-22 |
| What queries can a customer issue outside the provider UI? | Documented structured API filtersPandaDoc / document-list metadata and template-based document creation via production API keys; signed binaries and complete content-library migration are excluded. Filter by creation dates, template, folder or status; deleted=true selects deleted documents. | PandaDoc list and search documents ↗page, count, order_by, created_from and deletedChecked 2026-10-22 |
| Who decides whether a chosen third party may connect? | -PandaDoc / document-list metadata and template-based document creation via production API keys; signed binaries and complete content-library migration are excluded. The technical route is documented; eligibility and review for independently distributed third-party applications remain unresolved. | PandaDoc production API keys ↗Production API key setupChecked 2026-10-22 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -PandaDoc / document-list metadata and template-based document creation via production API keys; signed binaries and complete content-library migration are excluded. Minimum commercial entitlement and exact API charges were not established for the assessed route. | PandaDoc list and search documents ↗page, count, order_by, created_from and deletedChecked 2026-10-22 |
| Which external write operations are documented? | Create and update in one business domainPandaDoc / document-list metadata and template-based document creation via production API keys; signed binaries and complete content-library migration are excluded. Create documents from templates using the documented creation payload; creation is asynchronous. | PandaDoc create document ↗Create Document and asynchronous processingChecked 2026-10-22 |
| How can customers connect an application they build or choose? | Customer applications using fixed APIs without provider selectionPandaDoc / document-list metadata and template-based document creation via production API keys; signed binaries and complete content-library migration are excluded. The documented interface can connect customer application code within its authorization and resource scope. | PandaDoc production API keys ↗Production API key setupChecked 2026-10-22 |
| What mechanism supports repeatable extraction of changes? | Scheduled feeds or recurring extractsPandaDoc / document-list metadata and template-based document creation via production API keys; signed binaries and complete content-library migration are excluded. Repeat document searches and explicitly include deleted documents. Sorting by date_modified alone is not a durable change stream. | PandaDoc list and search documents ↗page, count, order_by, created_from and deletedChecked 2026-10-22 |
| How are integration limits disclosed? | -PandaDoc / document-list metadata and template-based document creation via production API keys; signed binaries and complete content-library migration are excluded. A numeric request budget and recovery contract were not established by the reviewed references. | PandaDoc list and search documents ↗page, count, order_by, created_from and deletedChecked 2026-10-22 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsPandaDoc / document-list metadata and template-based document creation via production API keys; signed binaries and complete content-library migration are excluded. The assessed structured payloads can be retained in customer-held files. Broader contractual reuse rights remain unresolved. | PandaDoc list and search documents ↗page, count, order_by, created_from and deletedChecked 2026-10-22 |
| What retrieval rights are documented at cancellation? | -PandaDoc / document-list metadata and template-based document creation via production API keys; signed binaries and complete content-library migration are excluded. The reviewed technical documentation does not establish retrieval rights after account termination. | PandaDoc production API keys ↗Production API key setupChecked 2026-10-22 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedPandaDoc / document-list metadata and template-based document creation via production API keys; signed binaries and complete content-library migration are excluded. External code can use this interface; native workflow portability was not established (API clients and native definitions are different artifacts). | PandaDoc production API keys ↗Production API key setupChecked 2026-10-22 |
| What rights or portability are documented for custom workflow artifacts? | -PandaDoc / document-list metadata and template-based document creation via production API keys; signed binaries and complete content-library migration are excluded. Ownership and reusable export rights for native workflow artifacts need a separate contractual review. | PandaDoc production API keys ↗Production API key setupChecked 2026-10-22 |
| What usable data or native definitions can leave before cancellation? | Portable structured records on documented routes; whole-product completeness unverifiedPandaDoc / document-list metadata and template-based document creation via production API keys; signed binaries and complete content-library migration are excluded. Retain the assessed structured records before losing access. Attachments, historical versions, permissions and full product configuration need separate extraction. | PandaDoc list and search documents ↗page, count, order_by, created_from and deletedChecked 2026-10-22 |
| What permission is needed for the documented downstream use? | -PandaDoc / document-list metadata and template-based document creation via production API keys; signed binaries and complete content-library migration are excluded. Processing, AI-use, redistribution and other downstream contractual permissions were not settled by this technical review. | PandaDoc production API keys ↗Production API key setupChecked 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.