Business API Design Specification - `Create Lobbymessage`

A Business API is a set of logical actions centered around a main data object. These actions can range from simple CRUD operations to complex workflows that implement intricate business logic.

While the term “API” traditionally refers to an interface that allows software systems to interact, in Mindbricks a Business API represents a broader concept. It encapsulates a business workflow around a data object, going beyond basic CRUD operations to include rich, internally coordinated actions that can be fully designed and customized.

This document provides an in-depth explanation of the architectural design of the createLobbyMessage Business API. It is intended to guide backend architects and developers in maintaining the current design. Additionally, frontend developers and frontend AI agents can use this document to understand how to properly consume this API on the client side.

Main Data Object and CRUD Operation

The createLobbyMessage Business API is designed to handle a create operation on the LobbyMessage data object. This operation is performed under the specified conditions and may include additional, coordinated actions as part of the workflow.

API Description

Post a new lobby chat message. Enforces mute (mutedUntil > now), ensures message is not empty and under 500 chars. SenderId and senderDisplayName are populated from session.

API Frontend Description By The Backend Architect

Attempts to send a message as a muted user yield an immediate error and UI block for sending.
Messages must be non-empty, max 500 chars.
Name shown is from session context at send time (persists if user later changes display name).
Guests allowed; no editing or “threading”.
No images/files — plain text only.

API Options

Auto Params : true Determines whether input parameters should be auto-generated from the schema of the associated data object. Set to false if you want to define all input parameters manually.
Raise Api Event : true Indicates whether the Business API should emit an API-level event after successful execution. This is typically used for audit trails, analytics, or external integrations. The event will be emitted to the lobbymessage-created Kafka Topic Note that the DB-Level events for create, update and delete operations will always be raised for internal reasons.
Active Check : `` Controls how the system checks if a record is active (not soft-deleted or inactive). Uses the ApiCheckOption to determine whether this is checked during the query or after fetching the instance.
Read From Entity Cache : false If enabled, the API will attempt to read the target object from the Redis entity cache before querying the database. This can improve performance for frequently accessed records.

API Controllers

A Mindbricks Business API can be accessed through multiple interfaces, including REST, gRPC, WebSocket, Kafka, or Cron. The controllers listed below map the business workflow to a specific interface, enabling consistent interaction regardless of the communication channel.

REST Controller

The createLobbyMessage Business API includes a REST controller that can be triggered via the following route:

/v1/lobbymessages

By sending a request to this route using the service API address, you can execute this Business API. Parameters can be provided in multiple HTTP locations, including the URL path, URL query, request body, and request headers. Detailed information about these parameters is provided in the Parameters section.

MCP Tool

REST controllers also expose the Business API as a tool in the MCP, making it accessible to AI agents. This createLobbyMessage Business API will be registered as a tool on the MCP server within the service binding.

API Parameters

The createLobbyMessage Business API has 9 parameters that must be sent from the controller. Note that all parameters, except session and Redis parameters, should be provided by the client.

Business API parameters can be:

Auto-generated by Mindbricks — inferred from the CRUD type and the property definitions of the main data object when the autoParameters option is enabled.
Custom parameters added by the architect — these can supplement or override the auto-generated parameters.

Regular Parameters

Name	Type	Required	Default	Location	Data Path

`lobbyMessageId`	`ID`	`No`	`-`	`body`	`lobbyMessageId`
Description:	This id paremeter is used to create the data object with a given specific id. Leave null for automatic id.

`senderId`	`ID`	`Yes`	`-`	`body`	`senderId`
Description:	User ID (guest or registered) who sent the message. References auth:user.id.

`senderDisplayName`	`String`	`Yes`	`-`	`body`	`senderDisplayName`
Description:	Display name (from user fullname at send time; allows historical display even if name changes).

`content`	`String`	`Yes`	`-`	`body`	`content`
Description:	Chat message body (limited at UI, backend-enforces not empty; max 500 chars).

`sentAt`	`Date`	`Yes`	`-`	`body`	`sentAt`
Description:	UTC timestamp when message was sent. Used to enforce 24h retention and sorting.

`reportStatus`	`Enum`	`Yes`	`-`	`body`	`reportStatus`
Description:	Moderation/report workflow state: none (default), reported (user), underReview (admin).

`mutedUntil`	`Date`	`No`	`-`	`body`	`mutedUntil`
Description:	If set, the message sender is muted in the lobby until this timestamp. Only admins may set. Used with senderId for lookup on enforcement.

`removed`	`Boolean`	`Yes`	`-`	`body`	`removed`
Description:	If true, message is hidden/removed by admin moderation (soft-remove).

`roomId`	`String`	`Yes`	`-`	`body`	`roomId`
Description:	Daily room identifier (lobby-YYYY-MM-DD). Scopes message to that day.

Parameter Transformations

Some parameters are post-processed using transform scripts after being read from the request but before validation or workflow execution. Only parameters with a transform script are listed below.

No parameters are transformed in this API.

AUTH Configuration

The authentication and authorization configuration defines the core access rules for the createLobbyMessage Business API. These checks are applied after parameter validation and before executing the main business logic.

While these settings cover the most common scenarios, more fine-grained or conditional access control—such as permissions based on object context, nested memberships, or custom workflows—should be implemented using explicit actions like PermissionCheckAction, MembershipCheckAction, or ObjectPermissionCheckAction.

This API requires login (loginRequired = true). Requests from non-logged-in users will return a 401 Unauthorized error. Login is necessary but not sufficient, as additional role, permission, or other authorization checks may still apply.

Ownership Checks

Role and Permission Settings

Absolute roles (bypass all auth checks):
Users with any of the following roles will bypass all authentication and authorization checks, including ownership, membership, and standard role/permission checks:
[superAdmin]

Data Clause

Defines custom field-value assignments used to modify or augment the default payload for create and update operations. These settings override values derived from the session or parameters if explicitly provided.", Note that a default data clause is always prepared by Mindbricks using data property settings, however any property in the data clause can be override by Data Clause Settings.

Custom Data Clause Override

{
    roomId: runMScript(() => (this.request.body.roomId), {"path":"services[2].businessLogic[0].dataClause.customData[0].value"}),
   
}

Actual Data Clause

The business api will use the following data clause. Note that any calculated value will be added to the data clause in the api manager.

{
  id: this.lobbyMessageId,
  senderId: this.senderId,
  senderDisplayName: this.senderDisplayName,
  content: this.content,
  sentAt: this.sentAt,
  reportStatus: this.reportStatus,
  mutedUntil: this.mutedUntil,
  removed: this.removed,
  roomId: runMScript(() => (this.request.body.roomId), {"path":"services[2].businessLogic[0].dataClause.customData[0].value"}),
}

Business Logic Workflow

[1] Step : startBusinessApi

Manager initializes context, populates session and request objects, prepares internal structures for parameter handling and workflow execution.

You can use the following settings to change some behavior of this step. `apiOptions`, `restSettings`, `grpcSettings`, `kafkaSettings`, `sseSettings`, `cronSettings`

[2] Step : readParameters

Manager reads input parameters, normalizes missing values, applies default type casting, and stores them in the API context.

You can use the following settings to change some behavior of this step. `customParameters`, `redisParameters`

[3] Step : transposeParameters

Manager transforms parameters, computes derived values, flattens or remaps arrays/objects, and adjusts formats for downstream processing.

[4] Step : checkParameters

Manager executes built-in validations: required field checks, type enforcement, and basic business rules. Prevents operation if validation fails.

[5] Action : validateMuteAndContent

Action Type: FunctionCallAction

Pre-send logic: throw error if user is muted (any unexpired mute found for sender) and check content meets requirements.

class Api {
  async validateMuteAndContent() {
    try {
      return runMScript(() => LIB.lobbyChatValidateMuteAndContent(this), {
        path: "services[2].businessLogic[0].actions.functionCallActions[0].callScript",
      });
    } catch (err) {
      console.error("Error in FunctionCallAction validateMuteAndContent:", err);
      throw err;
    }
  }
}

[6] Step : checkBasicAuth

Manager performs authentication and authorization checks: verifies session, user roles, permissions, and tenant restrictions.

You can use the following settings to change some behavior of this step. `authOptions`

[7] Step : buildDataClause

Manager constructs the final data object for creation, fills auto-generated fields (IDs, timestamps, owner fields), and ensures schema consistency.

You can use the following settings to change some behavior of this step. `dataClause`

[8] Step : mainCreateOperation

Manager executes the database insert operation, updates indexes/caches, and triggers internal post-processing like linked default records.

[9] Step : buildOutput

Manager shapes the response: masks sensitive fields, resolves linked references, and formats output according to API contract.

[10] Step : sendResponse

Manager sends the response to the client and finalizes internal tasks like flushing logs or updating session state.

[11] Step : raiseApiEvent

Manager triggers API-level events (Kafka, WebSocket, async workflows) as the final internal step.

Rest Usage

Rest Client Parameters

Client parameters are the api parameters that are visible to client and will be populated by the client. Note that some api parameters are not visible to client because they are populated by internal system, session, calculation or joint sources.

The createLobbyMessage api has got 8 regular client parameters

Parameter	Type	Required	Population
senderId	ID	true	request.body?.[“senderId”]
senderDisplayName	String	true	request.body?.[“senderDisplayName”]
content	String	true	request.body?.[“content”]
sentAt	Date	true	request.body?.[“sentAt”]
reportStatus	Enum	true	request.body?.[“reportStatus”]
mutedUntil	Date	false	request.body?.[“mutedUntil”]
removed	Boolean	true	request.body?.[“removed”]
roomId	String	true	request.body?.[“roomId”]

REST Request

To access the api you can use the REST controller with the path POST /v1/lobbymessages

  axios({
    method: 'POST',
    url: '/v1/lobbymessages',
    data: {
            senderId:"ID",  
            senderDisplayName:"String",  
            content:"String",  
            sentAt:"Date",  
            reportStatus:"Enum",  
            mutedUntil:"Date",  
            removed:"Boolean",  
            roomId:"String",  
    
    },
    params: {
    
        }
  });

REST Response

The API response is encapsulated within a JSON envelope. Successful operations return an HTTP status code of 200 for get, list, update, or delete requests, and 201 for create requests. Each successful response includes a "status": "OK" property. For error handling, refer to the “Error Response” section.

Following JSON represents the most comprehensive form of the lobbyMessage object in the respones. However, some properties may be omitted based on the object’s internal logic.

{
	"status": "OK",
	"statusCode": "201",
	"elapsedMs": 126,
	"ssoTime": 120,
	"source": "db",
	"cacheKey": "hexCode",
	"userId": "ID",
	"sessionId": "ID",
	"requestId": "ID",
	"dataName": "lobbyMessage",
	"method": "POST",
	"action": "create",
	"appVersion": "Version",
	"rowCount": 1,
	"lobbyMessage": {
		"id": "ID",
		"senderId": "ID",
		"senderDisplayName": "String",
		"content": "String",
		"sentAt": "Date",
		"reportStatus": "Enum",
		"reportStatus_idx": "Integer",
		"mutedUntil": "Date",
		"removed": "Boolean",
		"roomId": "String",
		"recordVersion": "Integer",
		"createdAt": "Date",
		"updatedAt": "Date",
		"_owner": "ID",
		"isActive": true
	}
}

Business API Design Specification - Create Lobbymessage