curl --request GET \
--url 'https://api.scanova.io/webhook/slack/status/' \
--header 'Authorization: YOUR_API_KEY'
{
"connected": true,
"workspace": {
"id": 3,
"team_id": "T0123ABC",
"team_name": "Acme Inc",
"team_domain": "acme",
"authed_user_id": "U0456DEF",
"status": "connected",
"reauth_required": false,
"is_connected": true,
"created": "2026-06-01T10:00:00+05:30",
"modified": "2026-09-09T08:00:00+05:30"
}
}
{ "connected": false, "workspace": null }
Integrations
Slack connection status
GET /webhook/slack/status/
GET
/
webhook
/
slack
/
status
/
curl --request GET \
--url 'https://api.scanova.io/webhook/slack/status/' \
--header 'Authorization: YOUR_API_KEY'
{
"connected": true,
"workspace": {
"id": 3,
"team_id": "T0123ABC",
"team_name": "Acme Inc",
"team_domain": "acme",
"authed_user_id": "U0456DEF",
"status": "connected",
"reauth_required": false,
"is_connected": true,
"created": "2026-06-01T10:00:00+05:30",
"modified": "2026-09-09T08:00:00+05:30"
}
}
{ "connected": false, "workspace": null }
Returns the account’s Slack workspace connection status. Connecting or disconnecting Slack itself is not available on the Scanova API — it requires the browser OAuth flow in the dashboard (see API overview) — but everything downstream of an existing connection (this status check, channels, notification rules) is.
Requires authentication only. Live-refreshes the workspace’s identity from Slack on every call (not just a stored value).
curl --request GET \
--url 'https://api.scanova.io/webhook/slack/status/' \
--header 'Authorization: YOUR_API_KEY'
{
"connected": true,
"workspace": {
"id": 3,
"team_id": "T0123ABC",
"team_name": "Acme Inc",
"team_domain": "acme",
"authed_user_id": "U0456DEF",
"status": "connected",
"reauth_required": false,
"is_connected": true,
"created": "2026-06-01T10:00:00+05:30",
"modified": "2026-09-09T08:00:00+05:30"
}
}
{ "connected": false, "workspace": null }
reauth_required: true means the workspace’s token was revoked or expired — the account owner needs to reconnect through the dashboard.
Related
- Slack channels
- Slack notification rules
- 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: YOUR_API_KEY. 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
200 - application/json
Connection status.
Was this page helpful?