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
Notion / customer internal connection, selected pages and data sources, page-change webhooks and Markdown/CSV exports; public Marketplace distribution and agent APIs are outside this assessment.
Data sources return structured page records.
Query a Notion data source ↗
Query a data source · Checked 2026-10-16
Bulk delivery 8.8/10
Batched or iterable API requests
Notion / customer internal connection, selected pages and data sources, page-change webhooks and Markdown/CSV exports; public Marketplace distribution and agent APIs are outside this assessment.
Cursor traversal supports repeated reads of the shared data source.
Query a Notion data source ↗
Pagination · Checked 2026-10-16
Query expressiveness 8.8/10
Documented structured API filters
Notion / customer internal connection, selected pages and data sources, page-change webhooks and Markdown/CSV exports; public Marketplace distribution and agent APIs are outside this assessment.
Structured filters and sort orders are documented.
Query a Notion data source ↗
Filters and sorts · Checked 2026-10-16
Access cost barrier -
-
Notion / customer internal connection, selected pages and data sources, page-change webhooks and Markdown/CSV exports; public Marketplace distribution and agent APIs are outside this assessment.
Plan-specific budgets do not by themselves establish the full commercial entitlement.
Notion request limits ↗
Per-connection limit · Checked 2026-10-16
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
Notion / customer internal connection, selected pages and data sources, page-change webhooks and Markdown/CSV exports; public Marketplace distribution and agent APIs are outside this assessment.
The customer controls credentials or authorizes the application within existing resource permissions.
Notion authorization ↗
Internal connection auth flow set-up · Checked 2026-10-16
Downstream permission -
-
Notion / customer internal connection, selected pages and data sources, page-change webhooks and Markdown/CSV exports; public Marketplace distribution and agent APIs are outside this assessment.
Applicable third-party processing, AI use and redistribution terms remain unresolved.
Notion authorization ↗
Reviewed route documentation; downstream contractual scope unresolved · 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
Notion / customer internal connection, selected pages and data sources, page-change webhooks and Markdown/CSV exports; public Marketplace distribution and agent APIs are outside this assessment.
Page properties and page state can be updated with appropriate capabilities.
Update a Notion page ↗
Update page · Checked 2026-10-16
Custom application path 10.0/10
Customer applications using fixed APIs without provider selection
Notion / customer internal connection, selected pages and data sources, page-change webhooks and Markdown/CSV exports; public Marketplace distribution and agent APIs are outside this assessment.
Customers can connect an application using the documented token route.
Notion authorization ↗
Customer application authentication · 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
Notion / customer internal connection, selected pages and data sources, page-change webhooks and Markdown/CSV exports; public Marketplace distribution and agent APIs are outside this assessment.
Notifications identify pages whose state should be retrieved.
Notion webhooks ↗
How webhooks work · Checked 2026-10-16
Limit visibility 10.0/10
Published numeric quotas and recovery instructions
Notion / customer internal connection, selected pages and data sources, page-change webhooks and Markdown/CSV exports; public Marketplace distribution and agent APIs are outside this assessment.
Per connection: 600 requests/minute on Business/Enterprise and 180 on other plans. Shared workspace and endpoint limits also apply; 429/529 uses Retry-After.
Notion request limits ↗
Per-connection, per-workspace and rate limit responses · Checked 2026-10-16
CDC and deletion capture 7.5/10
Updates and deletion identities documented for the stated resources
Notion / customer internal connection, selected pages and data sources, page-change webhooks and Markdown/CSV exports; public Marketplace distribution and agent APIs are outside this assessment.
Page property/content updates and page.deleted carry entity identity; aggregation can omit transient states.
Notion event types and delivery ↗
Supported webhook event types · Checked 2026-10-16
Replay and gap recovery 5.0/10
Bounded redelivery or overlapping queries; no durable consumer checkpoint
Notion / customer internal connection, selected pages and data sources, page-change webhooks and Markdown/CSV exports; public Marketplace distribution and agent APIs are outside this assessment.
Up to eight retries end around 24 hours; no durable consumer-controlled replay checkpoint is established.
Notion event types and delivery ↗
Delivery retries · 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
Notion / customer internal connection, selected pages and data sources, page-change webhooks and Markdown/CSV exports; public Marketplace distribution and agent APIs are outside this assessment.
Structured files or API records can be held outside the provider.
Export your Notion content ↗
Customer download route · Checked 2026-10-16
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
Notion / customer internal connection, selected pages and data sources, page-change webhooks and Markdown/CSV exports; public Marketplace distribution and agent APIs are outside this assessment.
The export guide does not establish a contractual post-cancellation retrieval window.
Export your Notion content ↗
Reviewed export route; cancellation rights unresolved · Checked 2026-10-16
Planned migration fidelity 7.5/10
Portable structured records on documented routes; whole-product completeness unverified
Notion / customer internal connection, selected pages and data sources, page-change webhooks and Markdown/CSV exports; public Marketplace distribution and agent APIs are outside this assessment.
Customer-held Markdown/CSV is reusable content; whole-workspace reconstruction remains unverified.
Export your Notion content ↗
Export as Markdown and CSV · 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
Notion / customer internal connection, selected pages and data sources, page-change webhooks and Markdown/CSV exports; public Marketplace distribution and agent APIs are outside this assessment.
External customer code can call the documented API; native logic portability is not established.
Notion authorization ↗
Customer API integration · Checked 2026-10-16
Rights to custom logic -
-
Notion / customer internal connection, selected pages and data sources, page-change webhooks and Markdown/CSV exports; public Marketplace distribution and agent APIs are outside this assessment.
Ownership and reusable export of native workflow definitions require a separate contractual review.
Notion authorization ↗
Reviewed route documentation; artifact rights 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
A workspace owner creates an internal connection, then shares selected pages with it. OAuth public connections use a separate installation flow; the selected internal route needs customer authorization.
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
Data-source queries support filters, sorts and cursor traversal. Child blocks and large page properties need separate retrieval; a page response alone is not its complete content tree.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| Customer internal connection token | API key | Customer | No | Customer-supplied credentials | 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 request-limit documentation covers plans with different budgets. An explicit complete price and entitlement statement for the assessed route remains unresolved.
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
The page API updates properties and page state subject to connection capabilities. Other objects and API versions require their own operation 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
Page content/property updates and deletion notifications include entity IDs. Aggregation can collapse transient changes; retry delivery ends after eight attempts over approximately 24 hours.
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 resourcesNotion / customer internal connection, selected pages and data sources, page-change webhooks and Markdown/CSV exports; public Marketplace distribution and agent APIs are outside this assessment. Page property/content updates and page.deleted carry entity identity; aggregation can omit transient states. | Notion event types and delivery ↗Supported webhook event typesChecked 2026-10-16 |
| How can extraction recover after missed events or an interrupted consumer? | Bounded redelivery or overlapping queries; no durable consumer checkpointNotion / customer internal connection, selected pages and data sources, page-change webhooks and Markdown/CSV exports; public Marketplace distribution and agent APIs are outside this assessment. Up to eight retries end around 24 hours; no durable consumer-controlled replay checkpoint is established. | Notion event types and delivery ↗Delivery retriesChecked 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
Customers can export HTML or Markdown/CSV to local files. The export does not establish a one-step restore of workspace permissions, automations, comments or full version history.
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 run logic against shared pages and data sources. Native workflow ownership and reusable export remain unresolved (portable page content does not settle automation rights).
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 scopeNotion / customer internal connection, selected pages and data sources, page-change webhooks and Markdown/CSV exports; public Marketplace distribution and agent APIs are outside this assessment. Data sources return structured page records. | Query a Notion data source ↗Query a data sourceChecked 2026-10-16 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsNotion / customer internal connection, selected pages and data sources, page-change webhooks and Markdown/CSV exports; public Marketplace distribution and agent APIs are outside this assessment. Cursor traversal supports repeated reads of the shared data source. | Query a Notion data source ↗PaginationChecked 2026-10-16 |
| What queries can a customer issue outside the provider UI? | Documented structured API filtersNotion / customer internal connection, selected pages and data sources, page-change webhooks and Markdown/CSV exports; public Marketplace distribution and agent APIs are outside this assessment. Structured filters and sort orders are documented. | Query a Notion data source ↗Filters and sortsChecked 2026-10-16 |
| Who decides whether a chosen third party may connect? | Customer authorization without discretionary provider approvalNotion / customer internal connection, selected pages and data sources, page-change webhooks and Markdown/CSV exports; public Marketplace distribution and agent APIs are outside this assessment. The customer controls credentials or authorizes the application within existing resource permissions. | Notion authorization ↗Internal connection auth flow set-upChecked 2026-10-16 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -Notion / customer internal connection, selected pages and data sources, page-change webhooks and Markdown/CSV exports; public Marketplace distribution and agent APIs are outside this assessment. Plan-specific budgets do not by themselves establish the full commercial entitlement. | Notion request limits ↗Per-connection limitChecked 2026-10-16 |
| What permission is needed for the documented downstream use? | -Notion / customer internal connection, selected pages and data sources, page-change webhooks and Markdown/CSV exports; public Marketplace distribution and agent APIs are outside this assessment. Applicable third-party processing, AI use and redistribution terms remain unresolved. | Notion authorization ↗Reviewed route documentation; downstream contractual scope unresolvedChecked 2026-10-16 |
| Which external write operations are documented? | Named operations in a limited domainNotion / customer internal connection, selected pages and data sources, page-change webhooks and Markdown/CSV exports; public Marketplace distribution and agent APIs are outside this assessment. Page properties and page state can be updated with appropriate capabilities. | Update a Notion page ↗Update pageChecked 2026-10-16 |
| How can customers connect an application they build or choose? | Customer applications using fixed APIs without provider selectionNotion / customer internal connection, selected pages and data sources, page-change webhooks and Markdown/CSV exports; public Marketplace distribution and agent APIs are outside this assessment. Customers can connect an application using the documented token route. | Notion authorization ↗Customer application authenticationChecked 2026-10-16 |
| What mechanism supports repeatable extraction of changes? | Documented updated-since filters or webhooksNotion / customer internal connection, selected pages and data sources, page-change webhooks and Markdown/CSV exports; public Marketplace distribution and agent APIs are outside this assessment. Notifications identify pages whose state should be retrieved. | Notion webhooks ↗How webhooks workChecked 2026-10-16 |
| How are integration limits disclosed? | Published numeric quotas and recovery instructionsNotion / customer internal connection, selected pages and data sources, page-change webhooks and Markdown/CSV exports; public Marketplace distribution and agent APIs are outside this assessment. Per connection: 600 requests/minute on Business/Enterprise and 180 on other plans. Shared workspace and endpoint limits also apply; 429/529 uses Retry-After. | Notion request limits ↗Per-connection, per-workspace and rate limit responsesChecked 2026-10-16 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsNotion / customer internal connection, selected pages and data sources, page-change webhooks and Markdown/CSV exports; public Marketplace distribution and agent APIs are outside this assessment. Structured files or API records can be held outside the provider. | Export your Notion content ↗Customer download routeChecked 2026-10-16 |
| What retrieval rights are documented at cancellation? | -Notion / customer internal connection, selected pages and data sources, page-change webhooks and Markdown/CSV exports; public Marketplace distribution and agent APIs are outside this assessment. The export guide does not establish a contractual post-cancellation retrieval window. | Export your Notion content ↗Reviewed export route; cancellation rights unresolvedChecked 2026-10-16 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedNotion / customer internal connection, selected pages and data sources, page-change webhooks and Markdown/CSV exports; public Marketplace distribution and agent APIs are outside this assessment. External customer code can call the documented API; native logic portability is not established. | Notion authorization ↗Customer API integrationChecked 2026-10-16 |
| What rights or portability are documented for custom workflow artifacts? | -Notion / customer internal connection, selected pages and data sources, page-change webhooks and Markdown/CSV exports; public Marketplace distribution and agent APIs are outside this assessment. Ownership and reusable export of native workflow definitions require a separate contractual review. | Notion authorization ↗Reviewed route documentation; artifact rights unresolvedChecked 2026-10-16 |
| What usable data or native definitions can leave before cancellation? | Portable structured records on documented routes; whole-product completeness unverifiedNotion / customer internal connection, selected pages and data sources, page-change webhooks and Markdown/CSV exports; public Marketplace distribution and agent APIs are outside this assessment. Customer-held Markdown/CSV is reusable content; whole-workspace reconstruction remains unverified. | Export your Notion content ↗Export as Markdown and CSVChecked 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
- Applicable downstream processing, AI-use and redistribution terms
- Contractual retrieval rights after cancellation
- Ownership and reusable export of native workflow artifacts
- Complete attachment, history and configuration migration
- Complete commercial entitlement for the assessed API route
Documentation
Assessment checked 2026-10-16. Each answer retains its source and applicable route; the check date does not establish live account behavior.