Blacklist

Adds current session identity context to blacklist and may terminate the session.

Blacklist marks current session identity context as blacklisted for the application. This operation is available only after successful Initialize.

Request

Blacklist uses packet type = 6.

{
  "type": 6,
  "id": 7,
  "comment": "fraud detected"
}

Prop

Type

Response

{
  "id": 7,
  "status": 1
}

Prop

Type

Behavior notes

In blacklist-apply flows, server sends the operation response and then closes the session with close code 4203.
If request is rejected early (for example by quota), connection usually stays open and regular response is returned.

Blacklist statuses

Status	Constant	Returned when
`1`	`Ok`	Blacklist operation accepted.
`6`	`InternalServerError`	Server failed to process request due to an internal error.
`604`	`AppBlacklistsQuotaExceeded`	Application owner reached the application plan limit for blacklist entries.

Connection-close cases (before/around this usecase)

Blacklist can cause session close in addition to regular protocol/session guards:

Close code	Error	When it happens
`4200`	`connection is not initialized`	Request was sent before successful `Initialize`.
`4201`	`rate limit hit`	Global per-session packet rate limit was exceeded.
`4203`	`session was blacklisted`	Session was blacklisted by this operation and server terminated the connection.
`4302`	`invalid request body`	Packet body does not match the required schema for this operation.