---
id: "en/api-post-nd-api-file-send-dep-discussion"
title: "Send department discussion"
language: "en"
description: "POST /nd/api/file/send_dep_discussion: Send department discussion interface description, including path, method, parameters and return information."
canonical_url: "https://www.babel.cc/public/babelwiki/en/api-post-nd-api-file-send-dep-discussion.html"
markdown_url: "https://www.babel.cc/public/babelwiki/ai/en/api-post-nd-api-file-send-dep-discussion.md"
alternates: {"en": "https://www.babel.cc/public/babelwiki/ai/en/api-post-nd-api-file-send-dep-discussion.md", "zh": "https://www.babel.cc/public/babelwiki/ai/zh/api-post-nd-api-file-send-dep-discussion.md"}
reading_note: "文档记录不等于当前部署能力；以实际版本、授权模块与配置为准。保留原文的可选、限制及待确认说明，勿补猜接口。 / Documentation is not a guarantee for every deployment. Preserve optional-module requirements, limitations and unresolved API contracts."
---

# Send department discussion

`POST /nd/api/file/send_dep_discussion`

## POST body parameters

| Parameter | Type | Description |
| --- | --- | --- |
| `dep_id` | `string` | Required department ID |
| `message` | `string` | Required JSON string, e.g. {"Type":"Text","Body":"Hello"} |

## Response

Fields listed in the source: `code`, `messageId`, `success`.

message is a serialized string, not an unencoded nested object. Confirm the target department and text before sending.

## Calling the Endpoint

Use `Authorization: Bearer <access_token>`. GET parameters belong in the URL query; normal business POST requests use JSON. Check HTTP status and then the business result. Confirm array serialization and ambiguous types with the deployment instead of inventing fields.

[Authentication](https://www.babel.cc/public/babelwiki/en/developer-api-auth.html) · [API overview](https://www.babel.cc/public/babelwiki/en/developer-api-overview.html)