Skip to main content
Slack is in beta.
Create a Slack app for an Inkbox identity in a workspace configured by your organization. Search retained messages across the identity, or select a workspace connection for live operations and archive management. Start with the Slack guide for installation and runtime behavior. API base URL:
Authenticated requests use your API key:

Access

Claimed agent keys can reuse their organization’s saved workspaces, but can prepare, install, and use apps only for their own identity. Workspace metadata never includes saved credentials. Connections do not grant access outside the owning identity. Workspace approval, channel membership, granted Slack permissions, and Slack rate limits apply to every live operation. Unclaimed agent keys cannot use these endpoints. Retained reads also check current conversation access. Slack Connect uses the selected connection’s permissions. Slack does not apply email or phone contact allow/block rules to its conversations.

Endpoints

All paths below are relative to the API base URL. Register Slack events through the shared Webhook Subscriptions API, using agent_identity_id as owner.

Common errors and limits

An incompatible reuse of an idempotency key returns 409 with detail.error: "idempotency_key_reused". The SDKs expose the corresponding typed idempotency-conflict error. Do not retry it as a transient failure. Read one page at a time. The API does not promise a fixed requests-per-minute allowance or complete workspace history. Conversation objects and message objects contain the supported fields available from Slack, not a fixed set of populated properties. There are no Slack delivery/read receipts or semantic-search endpoints. Retained search covers captured message text, not every message or file in the workspace. Native processing status depends on Slack app and workspace support.