Slack

This documentation for the Slack integration describes the technical capabilities of this integration, including authorization, scopes/permissions, and utilized endpoints. For more information on how to integrate Slack, visit our connection instructions.

Version

This integration utilizes the Slack Web API.

Base URL

The base URL used for all Slack API endpoints:

https://slack.com/api

---

Authentication & Authorization

The Cyera Slack integration connects using OAuth 2.0.

Scopes

The Slack integration requires specific scopes that must be granted in order to function for a given capability.

Scope	Access
admin.apps:read
app_mentions:read
channels:history	✅
channels:read	✅
search:read	✅
team:read	✅
users:read	✅
users:read.email	✅

Endpoints Utilized

Cyera uses the following endpoints to authorize and test the connection:

Method	Endpoint	Purpose	Docs
GET	/auth.teams.list	List workspaces that the token can access
POST	/auth.test	Validate credentials
POST	/oauth.v2.access	Get and refresh access token
GET	/oauth/v2/authorize	Request authorization

---

Limits

Limits in Slack are calculated using the leaky bucket algorithm. All requests that are made after rate limits have been exceeded are throttled and an HTTP 429 Too Many Requests error is returned. Requests succeed again after enough requests have emptied out of the bucket.

• Cyera supports requests throttling to stay within 70-80% of specified service rate limits.
• Cyera processes API responses with HTTP 429 status to interrupt requests, waiting and retrying (using an exponential backoff strategy).

---

Capabilities

Access

Cyera's Slack integration provides Synchronous Access capabilities for the following supported identifier category: Email.

Data Interactions

For Access requests, Cyera will take the following actions:

1. Search for users by the data subject email address, if both scopes users:read and users:read.email are present.
2. If the scopes are present and a match is found, Cyera will fetch available workspaces and search for messages and files containing the data subject email and user ID.
3. If users:read and users:read.email are not present, Cyera will search available workspaces and public channels for messages and files containing the data subject email, filtering out false positives.

Endpoints Utilized

Method	Endpoint	Purpose	Docs
GET	/auth.teams.list	List available workspaces
POST	/conversations.list	Fetch the public channels list
POST	/search.all	Search for messages and files containing the data subject email
GET	/users.lookupByEmail	Search user by email

---