Skip to content

MngRejectAINotification

POST ai/notification/reject

Rejects a notification. It is never delivered, and the record is kept: the text shows what the assistant wanted to write and the reason shows why that was wrong.

That pair is the most useful material for improving prompts, so the interface should ask for a reason even though the method accepts an empty one.

Access Control

Allowed: manager, admin.

Request

POST request
POST https://{broker_domain}/ai/notification/reject
Authorization: <JWT_TOKEN>
Content-Type: application/json

{
  "id": "ntf_7c1…",
  "reason": "Reads like investment advice"
}
{
  "command": "MngRejectAINotification",
  "extID": "1",
  "data": { "id": "ntf_7c1…", "reason": "Reads like investment advice" }
}
await platform.MngRejectAINotification({ id, reason: 'Reads like investment advice' });

Parameters

Parameter Type Description
id string Notification id
reason string Optional, up to 512 characters

Response Data

{ "id": "ntf_7c1…", "state": "rejected" }

Errors

Code Error Description
400 AI_INVALID_DATA The notification is already sent or suppressed, or it does not exist in this brand
403 AI_ACCESS_DENIED The session is not an employee