integration-relay

Relay Route

Changed on

Record a thread→owner route created by a relay (local) mention.

When a mention runs on the desktop, cloud never sees the workspace, so the desktop reports the thread mapping here; without it, later replies in the thread have no route and cloud would drop them. First writer wins.

The caller may only record routes for a workspace it has a live Slack install in. The route is keyed on Slack coordinates alone, so without this check any authenticated API key could squat or mis-route another tenant's threads.

post/api/integrations/relay/route

Request

  • Base URL
    https://api.quadrillion.io (the document declares no server; this is the origin it was published from)
  • URL
    https://api.quadrillion.io/api/integrations/relay/route
  • Auth
    none declared

Request body

team_idstring required
channel_idstring required
thread_tsstring required
chat_session_idstring required

Response

Successful Response

Changes

  • abf76937a751Revision changes
    • info

      added the optional property // to the response with the status

    • info

      added the optional property // to the response with the status

  • bc8a81bf3914Revision changes
    • breaking

      added the new required request property

    • warning

      removed the request property