---
title: Messaging and Login API
description: Interface paths, methods, parameters and return fields of the messaging and login API.
slug: developer-api-jwt-status
lang: en
category: Messages And Login API
category_order: 8
order: 6
hide_in_nav: true
keywords:
  - API
  - Messaging and Login API
  - Developer
---


# Messages, Login and Status Codes

Department discussions and JWT web login. A signed JWT does not encrypt its payload. Generate it on a trusted server and explicitly identify the intended user. Check HTTP status separately from the JSON business code.

## Endpoints

| Method | Endpoint | Path |
| --- | --- | --- |
| `GET` | [JWT token login](api-get-account-tokenlogin-do.md) | `/account/tokenLogin.do` |
| `POST` | [Get department discussions](api-post-nd-api-file-dep-discussion.md) | `/nd/api/file/dep_discussion` |
| `POST` | [Send department discussion](api-post-nd-api-file-send-dep-discussion.md) | `/nd/api/file/send_dep_discussion` |

## Business Status Codes

| code | Meaning |
| --- | --- |
| 0 | Success |
| 1 | Unknown error |
| 2 | Invalid parameters |
| 7 | Insufficient space |
| 12 | Permission denied |
| 13 | Invalid token |

## Integration Notes

Based on the supplied Babel API reference. Preserve exact endpoint paths and field casing. Confirm unspecified or inconsistent field types during integration rather than assuming undocumented parameters. Use the deployment's HTTPS domain and keep credentials out of public pages.

[API overview](developer-api-overview.md) · [MCP quick start](mcp-integration.md)