`POST /v1/integrations/slack/interactions` (DAWG-313).
POST
/v1/integrations/slack/interactions
const url = 'https://api.updawg.net/v1/integrations/slack/interactions';const options = { method: 'POST', headers: {'Content-Type': 'application/x-www-form-urlencoded'}, body: new URLSearchParams('')};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request POST \ --url https://api.updawg.net/v1/integrations/slack/interactions \ --header 'Content-Type: application/x-www-form-urlencoded' \ --data ''Request Bodyrequired
Section titled “Request Bodyrequired”A click on a proposal’s message, or the reject form submitted, byte for byte as Slack signed it.
Media typeapplication/x-www-form-urlencoded
string
Responses
Section titled “Responses”Received, at once. What it came to goes back to Slack: a reply only the person sees, and the message edited when the proposal changes. For the reject form: clear, or errors when the reason is missing.
Media typeapplication/json
What the interactions route answers Slack with.
object
errors
For errors: the form’s field, and what is wrong with it.
object | null
response_action
clear closes the reject form; errors keeps it open saying why.
string | null
Example generated
{ "errors": "example", "response_action": "example"}Not signed by this region’s Slack app, more than five minutes old, or no payload.
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"}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"}