POST
/
v1
/
requests
/
slack
curl --request POST \
  --url https://api.siit.io/v1/requests/slack \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{
  "title": "<string>",
  "description": "<string>",
  "slack_user_id": "<string>",
  "slack_message_link": "<string>",
  "slack_channel_id": "<string>",
  "custom_form_inputs": [
    {
      "label": "<string>",
      "value": "<string>"
    }
  ]
}'
{
  "result": {
    "uid": "<string>",
    "title": "<string>",
    "description": "<string>",
    "priority": "low",
    "submitted_from": "employee_portal",
    "author_uid": "<string>",
    "requested_by_uid": "<string>",
    "assignee_admin_uid": "<string>",
    "assignee_inbox_uid": "<string>",
    "target_uid": "<string>",
    "admin_permalink_url": "<string>",
    "mode": "private",
    "status": "open",
    "friendly_id": "<string>",
    "slack_channel_id": "<string>",
    "slack_thread_ts": "<string>",
    "slack_ts": "<string>",
    "completed_at": "2023-11-07T05:31:56Z",
    "completed_by_uid": "<string>",
    "tag_uids": [
      "<string>"
    ],
    "custom_form_inputs": [
      {
        "label": "<string>",
        "kind": "attachment",
        "value": "<string>"
      }
    ],
    "sla_data": {
      "first_replied_at": "2023-11-07T05:31:56Z",
      "first_completed_at": "2023-11-07T05:31:56Z"
    },
    "updated_at": "2023-11-07T05:31:56Z",
    "created_at": "2023-11-07T05:31:56Z"
  }
}

​
Introduction

Use this route if you’re plugging the request submission using Slack Automation.

This avoid you having to fetch the user UIDs and instead directly use Slack User IDs.

A sample project interacting with this API is available here.

​
Usage

Authorizations

​
Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json

Response

201
application/json

Request created

The response is of type object.