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
Slack / permission-scoped conversation APIs and app-authored writes, Events API, and owner public-channel JSON download. Commercial third-party apps use Marketplace distribution; private-conversation Discovery exports require separate entitlement.
conversations.history returns cursor-paginated messages from conversations accessible to the token. Replies and files require separate calls.
Slack conversation history ↗
Arguments, cursor and time-range pagination · Checked 2026-10-16
Bulk delivery 2.5/10
Manual report download
Slack / permission-scoped conversation APIs and app-authored writes, Events API, and owner public-channel JSON download. Commercial third-party apps use Marketplace distribution; private-conversation Discovery exports require separate entitlement.
Owner public-channel JSON download supplies the manual bulk route. Ordinary externally offered apps cannot bulk export message/file API Data without an additional agreement.
Slack workspace exports ↗
Export availability and included data · Checked 2026-10-16
Query expressiveness 8.8/10
Documented structured API filters
Slack / permission-scoped conversation APIs and app-authored writes, Events API, and owner public-channel JSON download. Commercial third-party apps use Marketplace distribution; private-conversation Discovery exports require separate entitlement.
oldest/latest timestamp bounds select message history. This is scoped retrieval, without relational joins or full archive guarantees.
Slack conversation history ↗
Arguments, cursor and time-range pagination · Checked 2026-10-16
Access cost barrier -
-
Slack / permission-scoped conversation APIs and app-authored writes, Events API, and owner public-channel JSON download. Commercial third-party apps use Marketplace distribution; private-conversation Discovery exports require separate entitlement.
Owner public-channel JSON export and commercial app access are distinct routes. Additional agreements such as approved Discovery access are separate; full commercial conditions of the assessed portfolio remain unresolved.
Slack Web API limits ↗
App types, per-method quotas and Retry-After · Checked 2026-10-16
Third-party accessibility
20% of the overall score before applicability adjustment.
Scored answers and evidence
Third-party eligibility 7.5/10
Open registration under published review criteria
Slack / permission-scoped conversation APIs and app-authored writes, Events API, and owner public-channel JSON download. Commercial third-party apps use Marketplace distribution; private-conversation Discovery exports require separate entitlement.
Commercially distributed apps must follow Marketplace review requirements. Installation grants scopes and channel access; an internally built app does not establish eligibility for a commercial third party.
Slack Marketplace requirements ↗
Commercial distribution and review · Checked 2026-10-16
Downstream permission 7.5/10
Published purpose and confidentiality boundaries
Slack / permission-scoped conversation APIs and app-authored writes, Events API, and owner public-channel JSON download. Commercial third-party apps use Marketplace distribution; private-conversation Discovery exports require separate entitlement.
Same-customer application processing is bounded by the API terms. LLM training and cross-organization benefit are prohibited, while bulk export needs an additional agreement.
Slack API Terms of Service ↗
Application data use and commercial distribution · 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
Slack / permission-scoped conversation APIs and app-authored writes, Events API, and owner public-channel JSON download. Commercial third-party apps use Marketplace distribution; private-conversation Discovery exports require separate entitlement.
chat.postMessage publishes an app-authored message to an authorized channel; broader editing and deletion rights are outside this finding.
Slack post message operation ↗
Post a message and required scopes · Checked 2026-10-16
Custom application path 5.0/10
Approved third-party applications using fixed interfaces
Slack / permission-scoped conversation APIs and app-authored writes, Events API, and owner public-channel JSON download. Commercial third-party apps use Marketplace distribution; private-conversation Discovery exports require separate entitlement.
Third-party production applications use the documented provider approval route before the customer authorizes the fixed API interface.
Slack Marketplace requirements ↗
Commercial distribution and review · 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
Slack / permission-scoped conversation APIs and app-authored writes, Events API, and owner public-channel JSON download. Commercial third-party apps use Marketplace distribution; private-conversation Discovery exports require separate entitlement.
Events notify about permitted message activity. Retry delivery is bounded; enablement of delayed-event retries is a separate setting. Periodic history reconciliation is still necessary.
Slack Events API ↗
Retries and delayed events retry · Checked 2026-10-16
Limit visibility 10.0/10
Published numeric quotas and recovery instructions
Slack / permission-scoped conversation APIs and app-authored writes, Events API, and owner public-channel JSON download. Commercial third-party apps use Marketplace distribution; private-conversation Discovery exports require separate entitlement.
Limits apply per method/workspace/app, with 429 Retry-After. Commercial non-Marketplace history/replies have distinct restrictions; Events API permits 30,000 deliveries per workspace/app per 60 minutes.
Slack Web API limits ↗
App types, per-method quotas and Retry-After · Checked 2026-10-16
CDC and deletion capture -
-
Slack / permission-scoped conversation APIs and app-authored writes, Events API, and owner public-channel JSON download. Commercial third-party apps use Marketplace distribution; private-conversation Discovery exports require separate entitlement.
The reviewed Events overview does not establish complete update/deletion identity coverage across the declared message scope.
Slack Events API ↗
Retries and delayed events retry · Checked 2026-10-16
Replay and gap recovery 5.0/10
Bounded redelivery or overlapping queries; no durable consumer checkpoint
Slack / permission-scoped conversation APIs and app-authored writes, Events API, and owner public-channel JSON download. Commercial third-party apps use Marketplace distribution; private-conversation Discovery exports require separate entitlement.
Failed Events requests retry three times; optional delayed-event retries extend redelivery. Neither supplies a durable consumer replay checkpoint.
Slack Events API ↗
Retries and delayed events retry · 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
Slack / permission-scoped conversation APIs and app-authored writes, Events API, and owner public-channel JSON download. Commercial third-party apps use Marketplace distribution; private-conversation Discovery exports require separate entitlement.
Owner public-channel JSON exports supply a customer-held structured message copy. This exit credit excludes private channels, DMs, complete attachment bytes and history outside retention; ordinary app tokens do not provide unrestricted archival rights.
Slack workspace exports ↗
Export availability and included data · Checked 2026-10-16
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
Slack / permission-scoped conversation APIs and app-authored writes, Events API, and owner public-channel JSON download. Commercial third-party apps use Marketplace distribution; private-conversation Discovery exports require separate entitlement.
The reviewed extraction guide does not establish contractual retrieval rights after cancellation.
Slack workspace exports ↗
Export availability and included data · Checked 2026-10-16
Planned migration fidelity 7.5/10
Portable structured records on documented routes; whole-product completeness unverified
Slack / permission-scoped conversation APIs and app-authored writes, Events API, and owner public-channel JSON download. Commercial third-party apps use Marketplace distribution; private-conversation Discovery exports require separate entitlement.
Owner public-channel JSON exports supply a customer-held structured message copy. This exit credit excludes private channels, DMs, complete attachment bytes and history outside retention; ordinary app tokens do not provide unrestricted archival rights.
Slack workspace exports ↗
Export availability and included data · 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
Slack / permission-scoped conversation APIs and app-authored writes, Events API, and owner public-channel JSON download. Commercial third-party apps use Marketplace distribution; private-conversation Discovery exports require separate entitlement.
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).
Slack application authorization ↗
Permission model and authorizing applications · Checked 2026-10-16
Rights to custom logic -
-
Slack / permission-scoped conversation APIs and app-authored writes, Events API, and owner public-channel JSON download. Commercial third-party apps use Marketplace distribution; private-conversation Discovery exports require separate entitlement.
Native workflow ownership, reusable export and independent execution rights remain unresolved.
Slack application authorization ↗
Permission model and authorizing applications · 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
Commercially distributed apps must follow Marketplace review requirements. Installation grants scopes and channel access; an internally built app does not establish eligibility for a commercial third party.
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
conversations.history returns cursor-paginated messages from conversations accessible to the token. Replies and files require separate calls. oldest/latest timestamp bounds select message history. This is scoped retrieval, without relational joins or full archive guarantees.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| Customer-authorized application | OAuth 2.0 | Integration provider | Yes | App review | 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
Owner public-channel JSON export and commercial app access are distinct routes. Additional agreements such as approved Discovery access are separate; full commercial conditions of the assessed portfolio remain 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
chat.postMessage publishes an app-authored message to an authorized channel; broader editing and deletion rights are outside this finding.
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
Events notify about permitted message activity. Retry delivery is bounded; enablement of delayed-event retries is a separate setting. Periodic history reconciliation is still necessary. Limits apply per method/workspace/app, with 429 Retry-After. Commercial non-Marketplace history/replies have distinct restrictions; Events API permits 30,000 deliveries per workspace/app per 60 minutes.
CDC, deletions and recovery
| Question | Answer / applicable route | Evidence |
|---|---|---|
| Can ongoing extraction identify updates and deleted records on the declared route? | -Slack / permission-scoped conversation APIs and app-authored writes, Events API, and owner public-channel JSON download. Commercial third-party apps use Marketplace distribution; private-conversation Discovery exports require separate entitlement. The reviewed Events overview does not establish complete update/deletion identity coverage across the declared message scope. | Slack Events API ↗Retries and delayed events retryChecked 2026-10-16 |
| How can extraction recover after missed events or an interrupted consumer? | Bounded redelivery or overlapping queries; no durable consumer checkpointSlack / permission-scoped conversation APIs and app-authored writes, Events API, and owner public-channel JSON download. Commercial third-party apps use Marketplace distribution; private-conversation Discovery exports require separate entitlement. Failed Events requests retry three times; optional delayed-event retries extend redelivery. Neither supplies a durable consumer replay checkpoint. | Slack Events API ↗Retries and delayed events retryChecked 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
Owner public-channel JSON exports supply a customer-held structured message copy. This exit credit excludes private channels, DMs, complete attachment bytes and history outside retention; ordinary app tokens do not provide unrestricted archival rights.
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 scopeSlack / permission-scoped conversation APIs and app-authored writes, Events API, and owner public-channel JSON download. Commercial third-party apps use Marketplace distribution; private-conversation Discovery exports require separate entitlement. conversations.history returns cursor-paginated messages from conversations accessible to the token. Replies and files require separate calls. | Slack conversation history ↗Arguments, cursor and time-range paginationChecked 2026-10-16 |
| How can customers retrieve data in bulk? | Manual report downloadSlack / permission-scoped conversation APIs and app-authored writes, Events API, and owner public-channel JSON download. Commercial third-party apps use Marketplace distribution; private-conversation Discovery exports require separate entitlement. Owner public-channel JSON download supplies the manual bulk route. Ordinary externally offered apps cannot bulk export message/file API Data without an additional agreement. | Slack workspace exports ↗Export availability and included dataChecked 2026-10-16 |
| What queries can a customer issue outside the provider UI? | Documented structured API filtersSlack / permission-scoped conversation APIs and app-authored writes, Events API, and owner public-channel JSON download. Commercial third-party apps use Marketplace distribution; private-conversation Discovery exports require separate entitlement. oldest/latest timestamp bounds select message history. This is scoped retrieval, without relational joins or full archive guarantees. | Slack conversation history ↗Arguments, cursor and time-range paginationChecked 2026-10-16 |
| Who decides whether a chosen third party may connect? | Open registration under published review criteriaSlack / permission-scoped conversation APIs and app-authored writes, Events API, and owner public-channel JSON download. Commercial third-party apps use Marketplace distribution; private-conversation Discovery exports require separate entitlement. Commercially distributed apps must follow Marketplace review requirements. Installation grants scopes and channel access; an internally built app does not establish eligibility for a commercial third party. | Slack Marketplace requirements ↗Commercial distribution and reviewChecked 2026-10-16 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -Slack / permission-scoped conversation APIs and app-authored writes, Events API, and owner public-channel JSON download. Commercial third-party apps use Marketplace distribution; private-conversation Discovery exports require separate entitlement. Owner public-channel JSON export and commercial app access are distinct routes. Additional agreements such as approved Discovery access are separate; full commercial conditions of the assessed portfolio remain unresolved. | Slack Web API limits ↗App types, per-method quotas and Retry-AfterChecked 2026-10-16 |
| What permission is needed for the documented downstream use? | Published purpose and confidentiality boundariesSlack / permission-scoped conversation APIs and app-authored writes, Events API, and owner public-channel JSON download. Commercial third-party apps use Marketplace distribution; private-conversation Discovery exports require separate entitlement. Same-customer application processing is bounded by the API terms. LLM training and cross-organization benefit are prohibited, while bulk export needs an additional agreement. | Slack API Terms of Service ↗Application data use and commercial distributionChecked 2026-10-16 |
| Which external write operations are documented? | Named operations in a limited domainSlack / permission-scoped conversation APIs and app-authored writes, Events API, and owner public-channel JSON download. Commercial third-party apps use Marketplace distribution; private-conversation Discovery exports require separate entitlement. chat.postMessage publishes an app-authored message to an authorized channel; broader editing and deletion rights are outside this finding. | Slack post message operation ↗Post a message and required scopesChecked 2026-10-16 |
| How can customers connect an application they build or choose? | Approved third-party applications using fixed interfacesSlack / permission-scoped conversation APIs and app-authored writes, Events API, and owner public-channel JSON download. Commercial third-party apps use Marketplace distribution; private-conversation Discovery exports require separate entitlement. Third-party production applications use the documented provider approval route before the customer authorizes the fixed API interface. | Slack Marketplace requirements ↗Commercial distribution and reviewChecked 2026-10-16 |
| What mechanism supports repeatable extraction of changes? | Documented updated-since filters or webhooksSlack / permission-scoped conversation APIs and app-authored writes, Events API, and owner public-channel JSON download. Commercial third-party apps use Marketplace distribution; private-conversation Discovery exports require separate entitlement. Events notify about permitted message activity. Retry delivery is bounded; enablement of delayed-event retries is a separate setting. Periodic history reconciliation is still necessary. | Slack Events API ↗Retries and delayed events retryChecked 2026-10-16 |
| How are integration limits disclosed? | Published numeric quotas and recovery instructionsSlack / permission-scoped conversation APIs and app-authored writes, Events API, and owner public-channel JSON download. Commercial third-party apps use Marketplace distribution; private-conversation Discovery exports require separate entitlement. Limits apply per method/workspace/app, with 429 Retry-After. Commercial non-Marketplace history/replies have distinct restrictions; Events API permits 30,000 deliveries per workspace/app per 60 minutes. | Slack Web API limits ↗App types, per-method quotas and Retry-AfterChecked 2026-10-16 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsSlack / permission-scoped conversation APIs and app-authored writes, Events API, and owner public-channel JSON download. Commercial third-party apps use Marketplace distribution; private-conversation Discovery exports require separate entitlement. Owner public-channel JSON exports supply a customer-held structured message copy. This exit credit excludes private channels, DMs, complete attachment bytes and history outside retention; ordinary app tokens do not provide unrestricted archival rights. | Slack workspace exports ↗Export availability and included dataChecked 2026-10-16 |
| What retrieval rights are documented at cancellation? | -Slack / permission-scoped conversation APIs and app-authored writes, Events API, and owner public-channel JSON download. Commercial third-party apps use Marketplace distribution; private-conversation Discovery exports require separate entitlement. The reviewed extraction guide does not establish contractual retrieval rights after cancellation. | Slack workspace exports ↗Export availability and included dataChecked 2026-10-16 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedSlack / permission-scoped conversation APIs and app-authored writes, Events API, and owner public-channel JSON download. Commercial third-party apps use Marketplace distribution; private-conversation Discovery exports require separate entitlement. 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). | Slack application authorization ↗Permission model and authorizing applicationsChecked 2026-10-16 |
| What rights or portability are documented for custom workflow artifacts? | -Slack / permission-scoped conversation APIs and app-authored writes, Events API, and owner public-channel JSON download. Commercial third-party apps use Marketplace distribution; private-conversation Discovery exports require separate entitlement. Native workflow ownership, reusable export and independent execution rights remain unresolved. | Slack application authorization ↗Permission model and authorizing applicationsChecked 2026-10-16 |
| What usable data or native definitions can leave before cancellation? | Portable structured records on documented routes; whole-product completeness unverifiedSlack / permission-scoped conversation APIs and app-authored writes, Events API, and owner public-channel JSON download. Commercial third-party apps use Marketplace distribution; private-conversation Discovery exports require separate entitlement. Owner public-channel JSON exports supply a customer-held structured message copy. This exit credit excludes private channels, DMs, complete attachment bytes and history outside retention; ordinary app tokens do not provide unrestricted archival rights. | Slack workspace exports ↗Export availability and included dataChecked 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.