Skip to content
Updawg

`POST /v1/integrations/slack/events` (DAWG-319, DAWG-316, DAWG-317).

POST
/v1/integrations/slack/events
curl --request POST \
  --url https://api.updawg.net/v1/integrations/slack/events \
  --header 'Content-Type: application/json' \
  --data '"example"'

Request Bodyrequired

Section titled “Request Bodyrequired”

One of Slack’s Events API deliveries, byte for byte as Slack signed it.

Media typeapplication/json
string

Example generated

example

Responses

Section titled “Responses”

200

Section titled “200”

url_verification: its challenge, which is how Slack checks this address when the app’s manifest is saved. Anything else: {} at once, and the event acted on after — app_uninstalled and tokens_revoked remove the installation, app_home_opened draws the Home tab, link_shared unfurls a link to the portal.

Media typeapplication/json

What the events route answers Slack with (DAWG-319): challenge for its URL check, nothing for an event, which Slack only needs to see received.

object
challenge
string | null

Example generated

{
  "challenge": "example"
}

400

Section titled “400”

Not signed by this region’s Slack app, more than five minutes old, or not JSON.

Media typeapplication/json
object
detail
string | null
status
required
integer format: int32
title
required
string
type
required
string

Example generated

{
  "detail": "example",
  "status": 1,
  "title": "example",
  "type": "example"
}

503

Section titled “503”

This deployment has no Slack app: slack-unavailable.

Media typeapplication/json
object
detail
string | null
status
required
integer format: int32
title
required
string
type
required
string

Example generated

{
  "detail": "example",
  "status": 1,
  "title": "example",
  "type": "example"
}