curl --request POST \
--url 'https://api.scanova.io/webhook/slack/channels/sync/' \
--header 'Authorization: YOUR_API_KEY'
{
"channels": [
{ "id": "C0123ABC", "name": "general", "is_private": false, "is_member": true }
]
}
Integrations
Sync Slack channels
POST /webhook/slack/channels/sync/
POST
/
webhook
/
slack
/
channels
/
sync
/
curl --request POST \
--url 'https://api.scanova.io/webhook/slack/channels/sync/' \
--header 'Authorization: YOUR_API_KEY'
{
"channels": [
{ "id": "C0123ABC", "name": "general", "is_private": false, "is_member": true }
]
}
Fetches the connected workspace’s current channel list from Slack and re-caches it — call this before List Slack channels if you need up-to-date data.
If Slack reports the workspace’s token as revoked or invalid, the workspace is flagged
Requires the account’s
INTEGRATION_SLACK quota. No request body.curl --request POST \
--url 'https://api.scanova.io/webhook/slack/channels/sync/' \
--header 'Authorization: YOUR_API_KEY'
{
"channels": [
{ "id": "C0123ABC", "name": "general", "is_private": false, "is_member": true }
]
}
reauth_required: true (visible via Slack connection status) and this call returns 400.
404 if there’s no connected Slack workspace.
Related
- List Slack channels
- Slack connection status
- Management API overview — the auth scheme and quota architecture this endpoint is part of.
Authorizations
Send your Management API key as the raw value of the Authorization header — no "Bearer " or "Token " prefix, and no other characters. Example: Authorization: 401f7ac837da42b97f613d789819ff93537bee6a. A header containing more than one space-separated part is rejected outright. Requests also require the request's Host header to be the management API host (e.g. api.scanova.io) — the same key sent to the regular API host will not authenticate.
Response
Freshly-synced channel list.
Was this page helpful?