---
title: "Relay Route"
method: POST
path: "/api/integrations/relay/route"
tags: ["integration-relay"]
---

# Relay Route

`POST /api/integrations/relay/route`

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.

## Request body

- RouteBody
  - `team_id` string, required
  - `channel_id` string, required
  - `thread_ts` string, required
  - `chat_session_id` string, required

## Response `204`

Successful Response

## Other responses

- `422` — Validation Error

## Changes

- **2026-08-19** `bc8a81bf3914` — 1 breaking, 1 warning
  - added the new required request property `chat_session_id`
  - removed the request property `project_id`

[Change history](https://skmtc.dev/quadrillion/apis/quadrillion-cloud-api/changes/api/integrations/relay/route/post.md)

---

[API](https://skmtc.dev/quadrillion/apis/quadrillion-cloud-api.md) · [All operations](https://skmtc.dev/quadrillion/apis/quadrillion-cloud-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/quadrillion/quadrillion-cloud-api/revisions/f4de1bab5efb/schema)