---
title: "Relink Slack Identity"
method: POST
path: "/api/v1/recipients/slack/relink"
tags: ["recipients"]
---

# Relink Slack Identity

`POST /api/v1/recipients/slack/relink`

Forget the caller's own Slack mapping so the next send looks it up again.

Not admin-gated, and it needs no authorization code at all: `company_id` and
`user_id` both come from the verified scope, so this route can only ever
touch the caller's own row. That is also why it is a POST with no body.

`cleared: true` describes the state after the call, exactly like DELETE's
`disconnected: true`, and not whether a row moved: `clear_identity` is
idempotent, and "there was nothing cached" is a success — the next
notification looks the user up fresh either way.

Why the row is deleted rather than nulled, and why there is no
authorization code, both live in `clear_identity`.

## Response `200`

Successful Response

- object

## Changes

> 36 revisions in range; 1 not diffed.

- **2026-09-13** `2fbe8fef9481` — 1 info
  - endpoint added

[Change history](https://skmtc.dev/netter/apis/dmi-backend/changes/api/v1/recipients/slack/relink/post.md)

---

[API](https://skmtc.dev/netter/apis/dmi-backend.md) · [All operations](https://skmtc.dev/netter/apis/dmi-backend/llms.txt) · [OpenAPI document](https://skmtc.dev/netter/apis/dmi-backend/revisions/45183c028c46?raw)