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
Confluence Cloud / distributable OAuth 2.0 app, permission-scoped page REST v2 operations, CQL search and customer content exports; legacy Connect webhooks and Data Center are separate.
Page collections support cursor pagination and selected body representations. CQL searches content under current viewing permissions; comments and attachments need additional endpoints.
Confluence page REST operations ↗
Get pages, pagination and body representations · Checked 2026-10-16
Bulk delivery 8.8/10
Batched or iterable API requests
Confluence Cloud / distributable OAuth 2.0 app, permission-scoped page REST v2 operations, CQL search and customer content exports; legacy Connect webhooks and Data Center are separate.
Page collections support cursor pagination and selected body representations. CQL searches content under current viewing permissions; comments and attachments need additional endpoints.
Confluence page REST operations ↗
Get pages, pagination and body representations · Checked 2026-10-16
Query expressiveness 8.8/10
Documented structured API filters
Confluence Cloud / distributable OAuth 2.0 app, permission-scoped page REST v2 operations, CQL search and customer content exports; legacy Connect webhooks and Data Center are separate.
CQL supports fields such as space, type and lastmodified, with predicates and ordering. It does not provide general operational SQL joins.
Confluence page REST operations ↗
Get pages, pagination and body representations · Checked 2026-10-16
Access cost barrier -
-
Confluence Cloud / distributable OAuth 2.0 app, permission-scoped page REST v2 operations, CQL search and customer content exports; legacy Connect webhooks and Data Center are separate.
The technical sources do not establish all minimum-plan and fixed access conditions for the selected OAuth, page and export portfolio.
Confluence Cloud rate limiting ↗
Hourly point quotas, burst limits and retry handling · 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
Confluence Cloud / distributable OAuth 2.0 app, permission-scoped page REST v2 operations, CQL search and customer content exports; legacy Connect webhooks and Data Center are separate.
A distributable 3LO app can be shared through its authorization URL and acts within user permissions and requested scopes. Review can remove an unapproved-app warning; customer API-token collection is not the supported distributed-app route.
Confluence OAuth application authorization ↗
Sharing applications and user permissions · Checked 2026-10-16
Downstream permission -
-
Confluence Cloud / distributable OAuth 2.0 app, permission-scoped page REST v2 operations, CQL search and customer content exports; legacy Connect webhooks and Data Center are separate.
Applicable third-party processing, AI-use and redistribution terms require a separate contractual review.
Confluence OAuth application authorization ↗
Sharing applications and user permissions · Checked 2026-10-16
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
Confluence Cloud / distributable OAuth 2.0 app, permission-scoped page REST v2 operations, CQL search and customer content exports; legacy Connect webhooks and Data Center are separate.
REST v2 creates pages and updates existing pages with version information, body representation and write permissions.
Confluence create and update page ↗
Create page and update page · Checked 2026-10-16
Custom application path 10.0/10
Customer applications using fixed APIs without provider selection
Confluence Cloud / distributable OAuth 2.0 app, permission-scoped page REST v2 operations, CQL search and customer content exports; legacy Connect webhooks and Data Center are separate.
Customers can build or choose applications using the documented API and the disclosed authorization route.
Confluence OAuth application authorization ↗
Sharing applications and user permissions · 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
Confluence Cloud / distributable OAuth 2.0 app, permission-scoped page REST v2 operations, CQL search and customer content exports; legacy Connect webhooks and Data Center are separate.
CQL lastmodified filters support overlapping updated-page polling. Reconcile current/trash states separately; legacy Connect notifications do not establish a webhook route for a new 3LO app.
Confluence CQL search ↗
CQL fields, lastmodified and search conditions · Checked 2026-10-16
Limit visibility 10.0/10
Published numeric quotas and recovery instructions
Confluence Cloud / distributable OAuth 2.0 app, permission-scoped page REST v2 operations, CQL search and customer content exports; legacy Connect webhooks and Data Center are separate.
Current app limits use hourly points-based quotas and burst limits with response headers and retry guidance. Request cost and tenant context matter; one universal requests-per-second number is not established.
Confluence Cloud rate limiting ↗
Hourly point quotas, burst limits and retry handling · Checked 2026-10-16
CDC and deletion capture 5.0/10
Updates identified; deletion capture not established
Confluence Cloud / distributable OAuth 2.0 app, permission-scoped page REST v2 operations, CQL search and customer content exports; legacy Connect webhooks and Data Center are separate.
lastmodified queries identify changed content. Complete deletion identities for the assessed OAuth polling route remain unresolved.
Confluence CQL search ↗
CQL fields, lastmodified and search conditions · Checked 2026-10-16
Replay and gap recovery 2.5/10
Rebuild from a fresh snapshot; no historical replay established
Confluence Cloud / distributable OAuth 2.0 app, permission-scoped page REST v2 operations, CQL search and customer content exports; legacy Connect webhooks and Data Center are separate.
Current page enumeration and content export can rebuild the disclosed content scope; no retained ordered update/deletion replay is established.
Confluence CQL search ↗
CQL fields, lastmodified and search conditions · 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
Confluence Cloud / distributable OAuth 2.0 app, permission-scoped page REST v2 operations, CQL search and customer content exports; legacy Connect webhooks and Data Center are separate.
Customer exports offer Word/PDF and structured space data formats, while API page bodies are portable records. Macro behavior, permissions, attachments and full revision history are not proven completely restorable.
Confluence customer content export ↗
Exporting space content and format limitations · Checked 2026-10-16
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
Confluence Cloud / distributable OAuth 2.0 app, permission-scoped page REST v2 operations, CQL search and customer content exports; legacy Connect webhooks and Data Center are separate.
The reviewed extraction guide does not establish contractual retrieval rights after cancellation.
Confluence customer content export ↗
Exporting space content and format limitations · Checked 2026-10-16
Planned migration fidelity 7.5/10
Portable structured records on documented routes; whole-product completeness unverified
Confluence Cloud / distributable OAuth 2.0 app, permission-scoped page REST v2 operations, CQL search and customer content exports; legacy Connect webhooks and Data Center are separate.
Customer exports offer Word/PDF and structured space data formats, while API page bodies are portable records. Macro behavior, permissions, attachments and full revision history are not proven completely restorable.
Confluence customer content export ↗
Exporting space content and format limitations · 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
Confluence Cloud / distributable OAuth 2.0 app, permission-scoped page REST v2 operations, CQL search and customer content exports; legacy Connect webhooks and Data Center are separate.
Customers can implement external logic against the assessed API. Ownership and reusable export of native workflow artifacts remain unresolved (customer integration code does not establish those rights).
Confluence OAuth application authorization ↗
Sharing applications and user permissions · Checked 2026-10-16
Rights to custom logic -
-
Confluence Cloud / distributable OAuth 2.0 app, permission-scoped page REST v2 operations, CQL search and customer content exports; legacy Connect webhooks and Data Center are separate.
Native workflow ownership, reusable export and independent execution rights remain unresolved.
Confluence OAuth application authorization ↗
Sharing applications and user permissions · 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 distributable 3LO app can be shared through its authorization URL and acts within user permissions and requested scopes. Review can remove an unapproved-app warning; customer API-token collection is not the supported distributed-app route.
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
Page collections support cursor pagination and selected body representations. CQL searches content under current viewing permissions; comments and attachments need additional endpoints. CQL supports fields such as space, type and lastmodified, with predicates and ordering. It does not provide general operational SQL joins.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| Customer-authorized application | OAuth 2.0 | Integration provider | No | customer authorization | 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 technical sources do not establish all minimum-plan and fixed access conditions for the selected OAuth, page and export portfolio.
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
REST v2 creates pages and updates existing pages with version information, body representation and write permissions.
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
CQL lastmodified filters support overlapping updated-page polling. Reconcile current/trash states separately; legacy Connect notifications do not establish a webhook route for a new 3LO app. Current app limits use hourly points-based quotas and burst limits with response headers and retry guidance. Request cost and tenant context matter; one universal requests-per-second number is not established.
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 establishedConfluence Cloud / distributable OAuth 2.0 app, permission-scoped page REST v2 operations, CQL search and customer content exports; legacy Connect webhooks and Data Center are separate. lastmodified queries identify changed content. Complete deletion identities for the assessed OAuth polling route remain unresolved. | Confluence CQL search ↗CQL fields, lastmodified and search conditionsChecked 2026-10-16 |
| How can extraction recover after missed events or an interrupted consumer? | Rebuild from a fresh snapshot; no historical replay establishedConfluence Cloud / distributable OAuth 2.0 app, permission-scoped page REST v2 operations, CQL search and customer content exports; legacy Connect webhooks and Data Center are separate. Current page enumeration and content export can rebuild the disclosed content scope; no retained ordered update/deletion replay is established. | Confluence CQL search ↗CQL fields, lastmodified and search conditionsChecked 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 exports offer Word/PDF and structured space data formats, while API page bodies are portable records. Macro behavior, permissions, attachments and full revision history are not proven completely restorable.
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 implement external logic against the assessed API. Ownership and reusable export of native workflow artifacts remain unresolved (customer integration code does not establish those 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 scopeConfluence Cloud / distributable OAuth 2.0 app, permission-scoped page REST v2 operations, CQL search and customer content exports; legacy Connect webhooks and Data Center are separate. Page collections support cursor pagination and selected body representations. CQL searches content under current viewing permissions; comments and attachments need additional endpoints. | Confluence page REST operations ↗Get pages, pagination and body representationsChecked 2026-10-16 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsConfluence Cloud / distributable OAuth 2.0 app, permission-scoped page REST v2 operations, CQL search and customer content exports; legacy Connect webhooks and Data Center are separate. Page collections support cursor pagination and selected body representations. CQL searches content under current viewing permissions; comments and attachments need additional endpoints. | Confluence page REST operations ↗Get pages, pagination and body representationsChecked 2026-10-16 |
| What queries can a customer issue outside the provider UI? | Documented structured API filtersConfluence Cloud / distributable OAuth 2.0 app, permission-scoped page REST v2 operations, CQL search and customer content exports; legacy Connect webhooks and Data Center are separate. CQL supports fields such as space, type and lastmodified, with predicates and ordering. It does not provide general operational SQL joins. | Confluence page REST operations ↗Get pages, pagination and body representationsChecked 2026-10-16 |
| Who decides whether a chosen third party may connect? | Customer authorization without discretionary provider approvalConfluence Cloud / distributable OAuth 2.0 app, permission-scoped page REST v2 operations, CQL search and customer content exports; legacy Connect webhooks and Data Center are separate. A distributable 3LO app can be shared through its authorization URL and acts within user permissions and requested scopes. Review can remove an unapproved-app warning; customer API-token collection is not the supported distributed-app route. | Confluence OAuth application authorization ↗Sharing applications and user permissionsChecked 2026-10-16 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -Confluence Cloud / distributable OAuth 2.0 app, permission-scoped page REST v2 operations, CQL search and customer content exports; legacy Connect webhooks and Data Center are separate. The technical sources do not establish all minimum-plan and fixed access conditions for the selected OAuth, page and export portfolio. | Confluence Cloud rate limiting ↗Hourly point quotas, burst limits and retry handlingChecked 2026-10-16 |
| What permission is needed for the documented downstream use? | -Confluence Cloud / distributable OAuth 2.0 app, permission-scoped page REST v2 operations, CQL search and customer content exports; legacy Connect webhooks and Data Center are separate. Applicable third-party processing, AI-use and redistribution terms require a separate contractual review. | Confluence OAuth application authorization ↗Sharing applications and user permissionsChecked 2026-10-16 |
| Which external write operations are documented? | Create and update in one business domainConfluence Cloud / distributable OAuth 2.0 app, permission-scoped page REST v2 operations, CQL search and customer content exports; legacy Connect webhooks and Data Center are separate. REST v2 creates pages and updates existing pages with version information, body representation and write permissions. | Confluence create and update page ↗Create page and update pageChecked 2026-10-16 |
| How can customers connect an application they build or choose? | Customer applications using fixed APIs without provider selectionConfluence Cloud / distributable OAuth 2.0 app, permission-scoped page REST v2 operations, CQL search and customer content exports; legacy Connect webhooks and Data Center are separate. Customers can build or choose applications using the documented API and the disclosed authorization route. | Confluence OAuth application authorization ↗Sharing applications and user permissionsChecked 2026-10-16 |
| What mechanism supports repeatable extraction of changes? | Documented updated-since filters or webhooksConfluence Cloud / distributable OAuth 2.0 app, permission-scoped page REST v2 operations, CQL search and customer content exports; legacy Connect webhooks and Data Center are separate. CQL lastmodified filters support overlapping updated-page polling. Reconcile current/trash states separately; legacy Connect notifications do not establish a webhook route for a new 3LO app. | Confluence CQL search ↗CQL fields, lastmodified and search conditionsChecked 2026-10-16 |
| How are integration limits disclosed? | Published numeric quotas and recovery instructionsConfluence Cloud / distributable OAuth 2.0 app, permission-scoped page REST v2 operations, CQL search and customer content exports; legacy Connect webhooks and Data Center are separate. Current app limits use hourly points-based quotas and burst limits with response headers and retry guidance. Request cost and tenant context matter; one universal requests-per-second number is not established. | Confluence Cloud rate limiting ↗Hourly point quotas, burst limits and retry handlingChecked 2026-10-16 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsConfluence Cloud / distributable OAuth 2.0 app, permission-scoped page REST v2 operations, CQL search and customer content exports; legacy Connect webhooks and Data Center are separate. Customer exports offer Word/PDF and structured space data formats, while API page bodies are portable records. Macro behavior, permissions, attachments and full revision history are not proven completely restorable. | Confluence customer content export ↗Exporting space content and format limitationsChecked 2026-10-16 |
| What retrieval rights are documented at cancellation? | -Confluence Cloud / distributable OAuth 2.0 app, permission-scoped page REST v2 operations, CQL search and customer content exports; legacy Connect webhooks and Data Center are separate. The reviewed extraction guide does not establish contractual retrieval rights after cancellation. | Confluence customer content export ↗Exporting space content and format limitationsChecked 2026-10-16 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedConfluence Cloud / distributable OAuth 2.0 app, permission-scoped page REST v2 operations, CQL search and customer content exports; legacy Connect webhooks and Data Center are separate. Customers can implement external logic against the assessed API. Ownership and reusable export of native workflow artifacts remain unresolved (customer integration code does not establish those rights). | Confluence OAuth application authorization ↗Sharing applications and user permissionsChecked 2026-10-16 |
| What rights or portability are documented for custom workflow artifacts? | -Confluence Cloud / distributable OAuth 2.0 app, permission-scoped page REST v2 operations, CQL search and customer content exports; legacy Connect webhooks and Data Center are separate. Native workflow ownership, reusable export and independent execution rights remain unresolved. | Confluence OAuth application authorization ↗Sharing applications and user permissionsChecked 2026-10-16 |
| What usable data or native definitions can leave before cancellation? | Portable structured records on documented routes; whole-product completeness unverifiedConfluence Cloud / distributable OAuth 2.0 app, permission-scoped page REST v2 operations, CQL search and customer content exports; legacy Connect webhooks and Data Center are separate. Customer exports offer Word/PDF and structured space data formats, while API page bodies are portable records. Macro behavior, permissions, attachments and full revision history are not proven completely restorable. | Confluence customer content export ↗Exporting space content and format limitationsChecked 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 and redistribution terms
- Post-cancellation retrieval rights
- Native workflow artifact ownership and independent execution
- Whole-product completeness beyond the declared objects and routes
- Complete commercial entitlement for the assessed portfolio
Documentation
Assessment checked 2026-10-16. Each answer retains its source and applicable route; the check date does not establish live account behavior.