@xfloor/floor-memory-sdk-js 1.0.4 → 1.0.6

package/dist/api/DefaultApi.js

@@ -6,11 +6,14 @@ Object.defineProperty(exports, "__esModule", {
 exports["default"] = void 0;
 var _ApiClient = _interopRequireDefault(require("../ApiClient"));
 var _ChangePassword200Response = _interopRequireDefault(require("../model/ChangePassword200Response"));
+var _ConversationThreads200Response = _interopRequireDefault(require("../model/ConversationThreads200Response"));
 var _EditFloor400Response = _interopRequireDefault(require("../model/EditFloor400Response"));
+var _GetConversations200Response = _interopRequireDefault(require("../model/GetConversations200Response"));
 var _GetFloorInformation200Response = _interopRequireDefault(require("../model/GetFloorInformation200Response"));
 var _GetRecentEvents400Response = _interopRequireDefault(require("../model/GetRecentEvents400Response"));
 var _ResetPassword200Response = _interopRequireDefault(require("../model/ResetPassword200Response"));
 var _ResetPassword400Response = _interopRequireDefault(require("../model/ResetPassword400Response"));
+var _SendSignInValidationCode200Response = _interopRequireDefault(require("../model/SendSignInValidationCode200Response"));
 var _SendValidationCode200Response = _interopRequireDefault(require("../model/SendValidationCode200Response"));
 var _SendValidationCodeRequest = _interopRequireDefault(require("../model/SendValidationCodeRequest"));
 var _SignInWithEmail200Response = _interopRequireDefault(require("../model/SignInWithEmail200Response"));
@@ -27,7 +30,9 @@ function _createClass(e, r, t) { return r && _defineProperties(e.prototype, r),
 function _toPropertyKey(t) { var i = _toPrimitive(t, "string"); return "symbol" == _typeof(i) ? i : i + ""; }
 function _toPrimitive(t, r) { if ("object" != _typeof(t) || !t) return t; var e = t[Symbol.toPrimitive]; if (void 0 !== e) { var i = e.call(t, r || "default"); if ("object" != _typeof(i)) return i; throw new TypeError("@@toPrimitive must return a primitive value."); } return ("string" === r ? String : Number)(t); } /**
  * Floor Memory
- * The set APIs are used to develop Floor pds which can be used as their personal assistants.   This set of APIs are divided into two parts.  - Memory and  - Registration.   The developer has two ways of using the APIs for the app development. Developer can choose to the  Registration APIs for using the existing xfloor infracture or can implement custom Registration process. In the case of custom registration process, the developer is bound to provide proper authentication mechanisms and then send the user information to xlfoor.
+ * The set APIs are used to develop Floor pds which can be used as their personal assistants. This set of APIs are divided into two parts.
+ * - Memory and
+ * - Registration. The developer has two ways of using the APIs for the app development. Developer can choose to the Registration APIs for using the existing xfloor infracture or can implement custom Registration process. In the case of custom registration process, the developer is bound to provide proper authentication mechanisms and then send the user information to xlfoor.
  *
  * The version of the OpenAPI document: 1.0.0
  * Contact: contact@ipomo.in
@@ -40,7 +45,7 @@ function _toPrimitive(t, r) { if ("object" != _typeof(t) || !t) return t; var e
 /**
 * Default service.
 * @module api/DefaultApi
-* @version 1.0.4
+* @version 1.0.6
 */
 var DefaultApi = exports["default"] = /*#__PURE__*/function () {
   /**
@@ -56,22 +61,102 @@ var DefaultApi = exports["default"] = /*#__PURE__*/function () {
   }
 
   /**
-   * Callback function to receive the result of the changeEmail operation.
-   * @callback module:api/DefaultApi~changeEmailCallback
+   * Callback function to receive the result of the apiDeveloperCreateAppPost operation.
+   * @callback module:api/DefaultApi~apiDeveloperCreateAppPostCallback
    * @param {String} error Error message, if any.
    * @param {Object} data The data returned by the service call.
    * @param {String} response The complete HTTP response.
    */
 
   /**
-   * Change email ID
-   * Updates the email ID associated with an existing user account after validating a one-time activation code sent to the **new email address**.  This operation can only be performed by a **logged-in user**. When a user initiates an email change, an activation code is sent to the newly provided email ID. The email update takes effect only after the activation code is successfully validated.  If the activation code validation fails, the email ID remains unchanged.  ---  ### **Authentication**  This endpoint requires **Bearer Token authentication**.  ``` Authorization: Bearer <access_token> ```  ---  ### **Request Body**  ```json {   \"user_id\": \"string\",   \"new_email_id\": \"string\",   \"activation_code\": \"string\",   \"app_id\":\"string\" } ```  **Field Description**  * `user_id` – Unique identifier of the logged-in user * `new_email_id` – New email address to be associated with the account * `activation_code` – One-time activation code sent to the new email ID for verification  ---  ### **Flow Summary**  1. User is authenticated and logged in 2. User requests to change email ID 3. System sends an activation code to the **new email address** 4. User submits the activation code via this API 5. On successful validation, the email ID is updated  ---  ### **Successful Response**  On successful validation:  * The activation code is verified * The user’s email ID is updated immediately * A `success` string is returned confirming the email change  ---  ### **Error Response**  The API returns an error response if:  * The activation code is invalid or expired * The activation code does not match the user or email * The new email ID is already in use * Authorization fails or the bearer token is missing or invalid  In all error cases, the existing email ID remains unchanged.  --- ### **Behavior Notes**  * Requires a prior call to `/auth-service/send/validation/code` with the proper mode.  ---  ### **Security Notes (Recommended)**  * Activation codes are single-use and time-bound * Email changes require prior authentication * Rate limiting may be applied to prevent abuse  ---  ### **One-Line Summary**  > Changes a user’s email ID after validating an activation code sent to the new email address. 
-   * @param {String} newEmailId New Email ID
-   * @param {String} activationCode Validation code
-   * @param {module:api/DefaultApi~changeEmailCallback} callback The callback function, accepting three arguments: error, data, response
+   * Create App
+   * Create a custom app using APIs. A 13 digit app ID gets created which takes title and description the app. An icon of specified size needs to be uploaded.
+   * @param {String} inputInfo 
+   * @param {Object} opts Optional parameters
+   * @param {File} [icon] 
+   * @param {module:api/DefaultApi~apiDeveloperCreateAppPostCallback} callback The callback function, accepting three arguments: error, data, response
    * data is of type: {@link Object}
    */
   return _createClass(DefaultApi, [{
+    key: "apiDeveloperCreateAppPost",
+    value: function apiDeveloperCreateAppPost(inputInfo, opts, callback) {
+      opts = opts || {};
+      var postBody = null;
+      // verify the required parameter 'inputInfo' is set
+      if (inputInfo === undefined || inputInfo === null) {
+        throw new Error("Missing the required parameter 'inputInfo' when calling apiDeveloperCreateAppPost");
+      }
+      var pathParams = {};
+      var queryParams = {};
+      var headerParams = {};
+      var formParams = {
+        'input_info': inputInfo,
+        'icon': opts['icon']
+      };
+      var authNames = [];
+      var contentTypes = ['multipart/form-data'];
+      var accepts = ['application/json'];
+      var returnType = Object;
+      return this.apiClient.callApi('/api/developer/create/app', 'POST', pathParams, queryParams, headerParams, formParams, postBody, authNames, contentTypes, accepts, returnType, null, callback);
+    }
+
+    /**
+     * Callback function to receive the result of the apiDeveloperModifyAppPost operation.
+     * @callback module:api/DefaultApi~apiDeveloperModifyAppPostCallback
+     * @param {String} error Error message, if any.
+     * @param {Object} data The data returned by the service call.
+     * @param {String} response The complete HTTP response.
+     */
+
+    /**
+     * Modify Floorpod App
+     * Modify title, details or the app icon
+     * @param {String} inputInfo User ID, App ID, Title, Details. User ID and App ID are required parameters. Title/details are optional.
+     * @param {Object} opts Optional parameters
+     * @param {File} [file] Upload the new PNG icon file.
+     * @param {module:api/DefaultApi~apiDeveloperModifyAppPostCallback} callback The callback function, accepting three arguments: error, data, response
+     * data is of type: {@link Object}
+     */
+  }, {
+    key: "apiDeveloperModifyAppPost",
+    value: function apiDeveloperModifyAppPost(inputInfo, opts, callback) {
+      opts = opts || {};
+      var postBody = null;
+      // verify the required parameter 'inputInfo' is set
+      if (inputInfo === undefined || inputInfo === null) {
+        throw new Error("Missing the required parameter 'inputInfo' when calling apiDeveloperModifyAppPost");
+      }
+      var pathParams = {};
+      var queryParams = {};
+      var headerParams = {};
+      var formParams = {
+        'input_info': inputInfo,
+        'file': opts['file']
+      };
+      var authNames = [];
+      var contentTypes = ['multipart/form-data'];
+      var accepts = ['application/json'];
+      var returnType = Object;
+      return this.apiClient.callApi('/api/developer/modify/app', 'POST', pathParams, queryParams, headerParams, formParams, postBody, authNames, contentTypes, accepts, returnType, null, callback);
+    }
+
+    /**
+     * Callback function to receive the result of the changeEmail operation.
+     * @callback module:api/DefaultApi~changeEmailCallback
+     * @param {String} error Error message, if any.
+     * @param {Object} data The data returned by the service call.
+     * @param {String} response The complete HTTP response.
+     */
+
+    /**
+     * Change email ID
+     * Updates the email ID associated with an existing user account after validating a one-time activation code sent to the **new email address**.  This operation can only be performed by a **logged-in user**. When a user initiates an email change, an activation code is sent to the newly provided email ID. The email update takes effect only after the activation code is successfully validated.  If the activation code validation fails, the email ID remains unchanged.  ---  ### **Authentication**  This endpoint requires **Bearer Token authentication**.  ``` Authorization: Bearer <access_token> ```  ---  ### **Request Body**  ```json {   \"user_id\": \"string\",   \"new_email_id\": \"string\",   \"activation_code\": \"string\",   \"app_id\":\"string\" } ```  **Field Description**  * `user_id` – Unique identifier of the logged-in user * `new_email_id` – New email address to be associated with the account * `activation_code` – One-time activation code sent to the new email ID for verification  ---  ### **Flow Summary**  1. User is authenticated and logged in 2. User requests to change email ID 3. System sends an activation code to the **new email address** 4. User submits the activation code via this API 5. On successful validation, the email ID is updated  ---  ### **Successful Response**  On successful validation:  * The activation code is verified * The user’s email ID is updated immediately * A `success` string is returned confirming the email change  ---  ### **Error Response**  The API returns an error response if:  * The activation code is invalid or expired * The activation code does not match the user or email * The new email ID is already in use * Authorization fails or the bearer token is missing or invalid  In all error cases, the existing email ID remains unchanged.  --- ### **Behavior Notes**  * Requires a prior call to `/auth-service/send/validation/code` with the proper mode.  ---  ### **Security Notes (Recommended)**  * Activation codes are single-use and time-bound * Email changes require prior authentication * Rate limiting may be applied to prevent abuse  ---  ### **One-Line Summary**  > Changes a user’s email ID after validating an activation code sent to the new email address. 
+     * @param {String} newEmailId New Email ID
+     * @param {String} activationCode Validation code
+     * @param {module:api/DefaultApi~changeEmailCallback} callback The callback function, accepting three arguments: error, data, response
+     * data is of type: {@link Object}
+     */
+  }, {
     key: "changeEmail",
     value: function changeEmail(newEmailId, activationCode, callback) {
       var postBody = null;
@@ -177,6 +262,84 @@ var DefaultApi = exports["default"] = /*#__PURE__*/function () {
       return this.apiClient.callApi('/auth-service/password/change', 'POST', pathParams, queryParams, headerParams, formParams, postBody, authNames, contentTypes, accepts, returnType, null, callback);
     }
 
+    /**
+     * Callback function to receive the result of the conversationThreads operation.
+     * @callback module:api/DefaultApi~conversationThreadsCallback
+     * @param {String} error Error message, if any.
+     * @param {module:model/ConversationThreads200Response} data The data returned by the service call.
+     * @param {String} response The complete HTTP response.
+     */
+
+    /**
+     * Get the conversational threads
+     * ### Conversation Model  - A **Thread** represents a single conversational context. - A **Conversation** is the ordered exchange of messages within a thread. - Threads are scoped per user and per floor.  This API retrieves the list of **conversational threads** associated with a specific **user** within a specific **floor**.  A **thread** represents a persistent conversation context between the user and the system (agent/assistant) inside a floor. Each thread maintains its own history and state, allowing users to resume previous conversations without losing context.  The API returns **only thread metadata**, not the message content itself. This makes it suitable for:  * Displaying a conversation list or sidebar * Allowing users to select and resume past conversations * Managing conversational memory per floor  ---  ## Key Concepts  * **Thread**: A long-lived conversational context tied to a user and a floor * **Floor-scoped memory**: Conversations are isolated per floor; threads from one floor are not visible in another * **User-specific**: Threads are private to the requesting user  ---  ## Request Method  `GET`  ---  ## Request Parameters (Query Parameters)  | Parameter Name | Type   | Required | Description                                                                  | | -------------- | ------ | -------- | ---------------------------------------------------------------------------- | | `user_id`      | String | **Yes**  | Unique identifier of the user whose conversation threads are being requested | | `floor_id`     | String | **Yes**  | Identifier of the floor in which the conversations exist                     |  ---  ## Authorization & Access Rules  * The caller must be authenticated as the given `user_id` * A user can retrieve **only their own threads** * Threads are scoped to the provided `floor_id` * Threads from other floors or other users are not accessible  ---  ## Response Format  `application/json`  ---  ## Response Description  The response contains:  * The `user_id` for which threads were fetched * A list of thread metadata objects, sorted by **most recently updated first**  ---  ## Response Structure  ### Top-Level Fields  | Field     | Type   | Description                                                               | | --------- | ------ | ------------------------------------------------------------------------- | | `user_id` | String | Identifier of the user                                                    | | `threads` | Array  | List of conversation threads belonging to the user in the specified floor |  ---  ### Thread Object (`threads[]`)  | Field          | Type                | Description                                       | | -------------- | ------------------- | ------------------------------------------------- | | `thread_id`    | String              | Unique identifier of the conversation thread      | | `title`        | String              | Human-readable title summarizing the conversation | | `last_updated` | String (YYYY-MM-DD) | Date when the thread was last updated             |  ---  ## Sample Success Response  ```json {   \"user_id\": \"59\",   \"threads\": [     {       \"thread_id\": \"55\",       \"title\": \"elegant potentially hopelessly ambitious sneak\",       \"last_updated\": \"2025-04-26\"     },     {       \"thread_id\": \"79\",       \"title\": \"sans profitable alienated by even overstay miserly practical\",       \"last_updated\": \"2025-04-24\"     },     {       \"thread_id\": \"89\",       \"title\": \"although light uh-huh despite instead vol sorrowful\",       \"last_updated\": \"2025-02-16\"     }   ] } ```  ---  ## Typical Use Cases  * Show a **list of past conversations** in a chat UI * Allow users to **resume a previous thread** * Display conversation history grouped by floor * Build agent dashboards with user-specific memory  ---  ## Notes  * This API returns **metadata only**; message history is retrieved using a separate thread-messages API * If no threads exist, the `threads` array will be empty * Thread titles may be system-generated or user-editable depending on implementation  ---  ## Common Error Responses (Examples)  ### Missing Parameters  ```json {   \"status\": \"ERROR\",   \"message\": \"user_id and floor_id are required\" } ```  ### Unauthorised Access  ```json {   \"status\": \"ERROR\",   \"message\": \"Unauthorized access to conversation threads\" } ``` 
+     * @param {String} userId User ID
+     * @param {String} floorId Floor ID
+     * @param {module:api/DefaultApi~conversationThreadsCallback} callback The callback function, accepting three arguments: error, data, response
+     * data is of type: {@link module:model/ConversationThreads200Response}
+     */
+  }, {
+    key: "conversationThreads",
+    value: function conversationThreads(userId, floorId, callback) {
+      var postBody = null;
+      // verify the required parameter 'userId' is set
+      if (userId === undefined || userId === null) {
+        throw new Error("Missing the required parameter 'userId' when calling conversationThreads");
+      }
+      // verify the required parameter 'floorId' is set
+      if (floorId === undefined || floorId === null) {
+        throw new Error("Missing the required parameter 'floorId' when calling conversationThreads");
+      }
+      var pathParams = {};
+      var queryParams = {
+        'user_id': userId,
+        'floor_id': floorId
+      };
+      var headerParams = {};
+      var formParams = {};
+      var authNames = ['bearer'];
+      var contentTypes = [];
+      var accepts = ['application/json'];
+      var returnType = _ConversationThreads200Response["default"];
+      return this.apiClient.callApi('/agent/memory/threads', 'GET', pathParams, queryParams, headerParams, formParams, postBody, authNames, contentTypes, accepts, returnType, null, callback);
+    }
+
+    /**
+     * Callback function to receive the result of the getConversations operation.
+     * @callback module:api/DefaultApi~getConversationsCallback
+     * @param {String} error Error message, if any.
+     * @param {module:model/GetConversations200Response} data The data returned by the service call.
+     * @param {String} response The complete HTTP response.
+     */
+
+    /**
+     * Conversations
+     * This API returns the **full conversation history** for a specific **thread** belonging to a user within a floor.  A **thread** represents a persistent conversation session. Each item in the returned `conversation` array contains:  * The **user request payload** (user query + context) * The **assistant response payload** (full LLM completion object) * The **retrieval trace** (metadata of posts fetched/used for the answer, including scores and identifiers)  This endpoint is intended for **developers** building custom conversational UIs and tooling that require:  * Full conversation replay * Debug visibility into the assistant output object (`choices`, model info, etc.) * RAG explainability via `fetch_multiple_posts.results[]`  ---  ## Request Method  `GET`  ---  ## Query Parameters  | Parameter   | Type   | Required | Description                                                                 | | ----------- | ------ | -------- | --------------------------------------------------------------------------- | | `user_id`   | String | **Yes**  | Owner of the conversation thread. The thread must belong to this user.      | | `floor_id`  | String | **Yes**  | Floor identifier in which the thread exists. Threads are scoped to a floor. | | `thread_id` | String | **Yes**  | Thread identifier whose conversations should be returned.                   |  ---  ## Authorization & Access Rules  * The caller must be authenticated as the given `user_id` (or have equivalent developer/system permission). * A user can access **only their own threads**. * Cross-user or cross-floor access must be rejected.  ---  ## Response Format  `application/json`  ---  ## Response Description  Returns the thread-level conversation payload:  * `user_id`: the user who owns the thread * `thread_id`: the requested thread * `conversation`: ordered list of conversation entries (each entry = user object + assistant object)  ---  ## Response Schema  ### Top-Level Fields  | Field          | Type   | Description                  | | -------------- | ------ | ---------------------------- | | `user_id`      | String | Owner of the thread          | | `thread_id`    | String | Thread identifier            | | `conversation` | Array  | List of conversation entries |  ---  ## `conversation[]` Entry Structure  Each entry contains two objects: `user` and `assistant`.  ---  ### `user` Object  | Field              | Type   | Description                                                         | | ------------------ | ------ | ------------------------------------------------------------------- | | `context`          | Object | Context used when processing the query (floor metadata, mode, etc.) | | `user_query`       | String | The user’s query message                                            | | `user_id`          | String | User identifier (should match top-level `user_id`)                  | | `user_thread`      | String | Thread identifier (should match top-level `thread_id`)              | | `recorded_content` | String | Persisted user content (often same as `user_query`)                 |  #### `user.context`  | Field            | Type   | Description                                    | | ---------------- | ------ | ---------------------------------------------- | | `floor_id`       | String | Floor UID/slug where the conversation occurred | | `title`          | String | Floor title at the time of the query           | | `fid`            | String | Immutable internal floor ID                    | | `floor_category` | String | Floor category identifier                      | | `floor_mode`     | String | Floor mode indicator (example: `\"1\"`)          |  ---  ### `assistant` Object  This contains the **full completion response** plus retrieval details.  | Field                  | Type   | Description                                         | | ---------------------- | ------ | --------------------------------------------------- | | `id`                   | String | Completion id (e.g., `chatcmpl-*`)                  | | `object`               | String | Response type (e.g., `chat.completion`)             | | `created`              | Number | Timestamp when response was created (epoch seconds) | | `floor_mode`           | String | Floor mode applied for generation                   | | `model`                | String | Model identifier used                               | | `choices`              | Array  | Generated outputs and metadata                      | | `fetch_multiple_posts` | Object | Retrieval trace (if retrieval was performed)        | | `content_type`         | String | Retrieved content type (e.g., `post`)               |  ---  ## `assistant.choices[]`  | Field              | Type   | Description                                                                | | ------------------ | ------ | -------------------------------------------------------------------------- | | `index`            | Number | Choice index                                                               | | `message`          | Object | Assistant message content                                                  | | `finish_reason`    | String | Why generation stopped (`stop`, `length`, etc.)                            | | `ai_model_details` | Object | Model runtime parameters (temperature, top_p, max_tokens, penalties, etc.) | | `prompt_details`   | Object | Prompt configuration used (system prompt, system_prompt_id, etc.)          |  > **Note:** `prompt_details.system_prompt` may be large and is returned as-is for developer inspection.  ---  ## `assistant.fetch_multiple_posts`  Describes the retrieval operation performed for the query.  | Field          | Type   | Description                            | | -------------- | ------ | -------------------------------------- | | `content_type` | String | Type of retrieved content (`post`)     | | `query`        | String | Query used for retrieval               | | `status`       | String | Retrieval status (`success`, `failed`) | | `message`      | String | Retrieval message                      | | `results`      | Array  | List of matched posts and metadata     |  ---  ## `assistant.fetch_multiple_posts.results[]`  | Field        | Type   | Description                                                       | | ------------ | ------ | ----------------------------------------------------------------- | | `from_floor` | String | Indicates source floor relation (e.g., same floor / linked floor) | | `content`    | String | Raw JSON string of the matched post metadata/content              | | `author`     | String | Author id of the matched post                                     | | `block_type` | Number | Block type of the matched post                                    | | `pid`        | String | Post/document id                                                  | | `bid`        | String | Block id containing the post                                      | | `fid`        | String | Floor internal id where the post belongs                          | | `score`      | Number | Similarity score                                                  | | `match_type` | String | Match type (`text`, etc.)                                         |  ---  ## Sample Success Response  Your provided payload is the canonical example. It includes:  * the user query and floor context * the full assistant completion object * the full retrieval results with post metadata * the response shown covers a few important items.  ---  ## Common Error Responses  ### Missing Parameters  ```json {   \"status\": \"ERROR\",   \"message\": \"user_id, floor_id, and thread_id are required\" } ```  ### Unauthorized Access  ```json {   \"status\": \"ERROR\",   \"message\": \"Unauthorized access to thread\" } ```  ### Thread Not Found  ```json {   \"status\": \"ERROR\",   \"message\": \"Thread not found\" } ```  ---  ## Developer Notes (Important)  * The `content` field inside retrieval results is a **stringified JSON**. Developers may parse it to access fields such as `post_title`, `post_details`, etc. * `choices` may contain multiple outputs depending on backend configuration. * This API returns a “full debug payload” suitable for developers. If you later create a lightweight UI endpoint, it should strip execution details and return only `user_query`, `assistant.content`, and curated post references.  
+     * @param {Object} opts Optional parameters
+     * @param {String} [userId] 
+     * @param {String} [threadId] 
+     * @param {module:api/DefaultApi~getConversationsCallback} callback The callback function, accepting three arguments: error, data, response
+     * data is of type: {@link module:model/GetConversations200Response}
+     */
+  }, {
+    key: "getConversations",
+    value: function getConversations(opts, callback) {
+      opts = opts || {};
+      var postBody = null;
+      var pathParams = {};
+      var queryParams = {
+        'user_id': opts['userId'],
+        'thread_id': opts['threadId']
+      };
+      var headerParams = {};
+      var formParams = {};
+      var authNames = ['bearer'];
+      var contentTypes = [];
+      var accepts = ['application/json'];
+      var returnType = _GetConversations200Response["default"];
+      return this.apiClient.callApi('/agent/memory/conversations', 'GET', pathParams, queryParams, headerParams, formParams, postBody, authNames, contentTypes, accepts, returnType, null, callback);
+    }
+
     /**
      * Callback function to receive the result of the makeFloorPrivate operation.
      * @callback module:api/DefaultApi~makeFloorPrivateCallback
@@ -188,23 +351,33 @@ var DefaultApi = exports["default"] = /*#__PURE__*/function () {
     /**
      * Make floor Private
      * This API changes a floor’s visibility to **PRIVATE**.  It is used when a floor owner wants to **restrict access** to a floor that is currently public. After the update, the floor becomes private and is no longer accessible to non-authorized users (based on your platform’s access rules).  This endpoint is **state-changing**:  * If the floor is **PUBLIC**, it will be converted to **PRIVATE** * If the floor is already **PRIVATE**, the API returns success (idempotent) or an “already private” response depending on implementation  This API is commonly used in:  * Floor settings → “Privacy” toggle * Developer-managed pod workflows (app_id context) * Admin tools (if applicable)  ---  ## Request Method  `POST`  ---  ## Content-Type  `application/x-www-form-urlencoded` (or `multipart/form-data` if your system uses form-data) *(Document whichever you actually accept; below assumes standard form fields.)*  ---  ## Request Parameters (Form Fields)  | Field      | Type   | Required | Description                                                          | | ---------- | ------ | -------- | -------------------------------------------------------------------- | | `user_id`  | String | **Yes**  | User requesting the change. Must be the **owner** of the floor.      | | `floor_id` | String | **Yes**  | Public identifier of the floor to update.                            | | `app_id`   | String | No       | Calling application identifier (used for developer/pod integration). |  ---  ## Authorization Rules (Critical)  * The caller must be authenticated as `user_id` * **Only the floor owner** can change floor visibility * If the user is not the owner, the request must be rejected  ---  ## Behavior Rules  * Converts visibility from **PUBLIC → PRIVATE** * Does not modify floor content or blocks * Access enforcement for private floors is applied immediately after the change  **Idempotency**  * Calling this API multiple times should not cause repeated changes * If already private, the API should either:    * return success with a message like `\"already private\"`, or   * return a specific error/status indicating no-op  ---  ## Response Format  `application/json`  ---  ## Sample Success Response  *(Example — adjust to match your actual response format)*  ```json {   \"status\": \"SUCCESS\",   \"floor_id\": \"my_floor\",   \"visibility\": \"PRIVATE\",   \"message\": \"Floor is now private\" } ```  ---  ## Sample No-Op Response (Already Private)  ```json {   \"status\": \"SUCCESS\",   \"floor_id\": \"my_floor\",   \"visibility\": \"PRIVATE\",   \"message\": \"Floor is already private\" } ```  ---  ## Error Responses (Examples)  ### Not Authorized (Not Owner)  ```json {   \"status\": \"ERROR\",   \"message\": \"Only the floor owner can change floor visibility\" } ```  ### Floor Not Found  ```json {   \"status\": \"ERROR\",   \"message\": \"Floor not found\" } ```  ### Invalid Request  ```json {   \"status\": \"ERROR\",   \"message\": \"user_id and floor_id are required\" } ```  ---  ## Notes  * This API is intended to control floor visibility only; membership/invite rules (for private floors) are handled elsewhere. * `app_id` is provided for developer/pod applications and is optional unless enforced by your app model. * If you support floor types like `POD`, document whether pods are allowed to be private or not (some platforms restrict this). 
-     * @param {Object} opts Optional parameters
-     * @param {String} [floorId] Floor ID
-     * @param {String} [userId] User ID
-     * @param {String} [appId] App ID
+     * @param {String} floorId Floor ID
+     * @param {String} userId User ID
+     * @param {String} appId App ID
      * @param {module:api/DefaultApi~makeFloorPrivateCallback} callback The callback function, accepting three arguments: error, data, response
      * data is of type: {@link module:model/GetFloorInformation200Response}
      */
   }, {
     key: "makeFloorPrivate",
-    value: function makeFloorPrivate(opts, callback) {
-      opts = opts || {};
+    value: function makeFloorPrivate(floorId, userId, appId, callback) {
       var postBody = null;
+      // verify the required parameter 'floorId' is set
+      if (floorId === undefined || floorId === null) {
+        throw new Error("Missing the required parameter 'floorId' when calling makeFloorPrivate");
+      }
+      // verify the required parameter 'userId' is set
+      if (userId === undefined || userId === null) {
+        throw new Error("Missing the required parameter 'userId' when calling makeFloorPrivate");
+      }
+      // verify the required parameter 'appId' is set
+      if (appId === undefined || appId === null) {
+        throw new Error("Missing the required parameter 'appId' when calling makeFloorPrivate");
+      }
       var pathParams = {};
       var queryParams = {
-        'floor_id': opts['floorId'],
-        'user_id': opts['userId'],
-        'app_id': opts['appId']
+        'floor_id': floorId,
+        'user_id': userId,
+        'app_id': appId
       };
       var headerParams = {};
       var formParams = {};
@@ -226,23 +399,33 @@ var DefaultApi = exports["default"] = /*#__PURE__*/function () {
     /**
      * Make floor public
      * This API changes a floor’s visibility to **PUBLIC**.  It is used when a floor owner wants to **make a private floor accessible to everyone**. After the update, the floor becomes public and can be viewed and discovered by any user, subject to platform rules (search, feeds, pods, etc.).  This endpoint performs a **visibility state transition**:  * **PRIVATE → PUBLIC** * If the floor is already public, the operation is treated as **idempotent** (no state change).  This API is typically used from:  * Floor settings → Privacy / Visibility controls * Owner or admin tools * Developer or pod-based applications using `app_id`  ---  ## Request Method  `POST`  ---  ## Content-Type  `application/x-www-form-urlencoded` (or `multipart/form-data`, depending on your implementation)  ---  ## Request Parameters (Form Fields)  | Field      | Type   | Required | Description                                                                     | | ---------- | ------ | -------- | ------------------------------------------------------------------------------- | | `user_id`  | String | **Yes**  | User requesting the change. Must be the **owner** of the floor.                 | | `floor_id` | String | **Yes**  | Public identifier of the floor whose visibility is to be changed.               | | `app_id`   | String | No       | Identifier of the calling application (used mainly for pod/developer contexts). |  ---  ## Authorization Rules (Critical)  * The caller must be authenticated as `user_id` * **Only the floor owner** is allowed to change the floor’s visibility * Requests from non-owners must be rejected  ---  ## Behavior Rules  * Converts floor visibility from **PRIVATE → PUBLIC** * Does not modify floor content, blocks, or ownership * Visibility change takes effect immediately  ### Idempotency  * If the floor is already public, the API should:    * Return success with a message indicating no change, or   * Return a specific “already public” status (implementation-dependent)  ---  ## Response Format  `application/json`  ---  ## Sample Success Response  ```json {   \"status\": \"SUCCESS\",   \"floor_id\": \"my_floor\",   \"visibility\": \"PUBLIC\",   \"message\": \"Floor is now public\" } ```  ---  ## Sample No-Op Response (Already Public)  ```json {   \"status\": \"SUCCESS\",   \"floor_id\": \"my_floor\",   \"visibility\": \"PUBLIC\",   \"message\": \"Floor is already public\" } ```  ---  ## Error Responses (Examples)  ### Not Authorized (Not Owner)  ```json {   \"status\": \"ERROR\",   \"message\": \"Only the floor owner can change floor visibility\" } ```  ---  ### Floor Not Found  ```json {   \"status\": \"ERROR\",   \"message\": \"Floor not found\" } ```  ---  ### Invalid Request  ```json {   \"status\": \"ERROR\",   \"message\": \"user_id and floor_id are required\" } ```  ---  ## Notes for Developers  * This API controls **visibility only**. Membership, invitations, and moderation rules are handled by separate APIs. * `app_id` is optional and primarily used for developer-managed or pod floors. * Clients should refresh floor metadata (e.g., via `/api/floor/info`) after a successful visibility change.  ---  ### Mental Model (One Line)  > **This API answers: “Make this floor visible to everyone.”** 
-     * @param {Object} opts Optional parameters
-     * @param {String} [floorId] Floor ID
-     * @param {String} [userId] User ID
-     * @param {String} [appId] App ID
+     * @param {String} floorId Floor ID
+     * @param {String} userId User ID
+     * @param {String} appId App ID
      * @param {module:api/DefaultApi~makeFloorPublicCallback} callback The callback function, accepting three arguments: error, data, response
      * data is of type: {@link module:model/GetFloorInformation200Response}
      */
   }, {
     key: "makeFloorPublic",
-    value: function makeFloorPublic(opts, callback) {
-      opts = opts || {};
+    value: function makeFloorPublic(floorId, userId, appId, callback) {
       var postBody = null;
+      // verify the required parameter 'floorId' is set
+      if (floorId === undefined || floorId === null) {
+        throw new Error("Missing the required parameter 'floorId' when calling makeFloorPublic");
+      }
+      // verify the required parameter 'userId' is set
+      if (userId === undefined || userId === null) {
+        throw new Error("Missing the required parameter 'userId' when calling makeFloorPublic");
+      }
+      // verify the required parameter 'appId' is set
+      if (appId === undefined || appId === null) {
+        throw new Error("Missing the required parameter 'appId' when calling makeFloorPublic");
+      }
       var pathParams = {};
       var queryParams = {
-        'floor_id': opts['floorId'],
-        'user_id': opts['userId'],
-        'app_id': opts['appId']
+        'floor_id': floorId,
+        'user_id': userId,
+        'app_id': appId
       };
       var headerParams = {};
       var formParams = {};
@@ -304,25 +487,39 @@ var DefaultApi = exports["default"] = /*#__PURE__*/function () {
     /**
      * Rename floor
      * This API renames a floor by changing knowing the **floor identifier (floor_id)**.  It allows the **floor owner** to update the public-facing floor ID (slug/handle) from an old value to a new value. This is typically used when the owner wants to rebrand, reorganize, or correct the floor’s identifier.  ⚠️ **This operation affects how the floor is accessed and referenced externally**, so it must be performed carefully.  ---  ## Ownership & Authorization (Critical)  * The caller **must be authenticated** * **Only the floor owner** is allowed to rename a floor * Members, followers, or non-owners **cannot** perform this operation * Ownership is validated internally using `user_id`  > If the user is not the owner, the request must be rejected.  ---  ## Request Method  `POST`  ---  ## Content-Type  `application/x-www-form-urlencoded` (or equivalent form-data encoding)  ---  ## Request Parameters (Form Fields)  | Parameter | Type   | Required | Description                                                                     | | --------- | ------ | -------- | ------------------------------------------------------------------------------- | | `user_id` | String | **Yes**  | User requesting the rename. Must be the **owner** of the floor.                 | | `from`    | String | **Yes**  | Existing floor ID (current identifier to be renamed).                           | | `to`      | String | **Yes**  | New floor ID to assign to the floor.                                            | | `app_id`  | String | No       | Identifier of the calling application (used mainly for pod/developer contexts). |  ---  ## Rename Rules & Constraints  * The `from` floor ID **must exist** * The `to` floor ID **must be unique** and not already in use * The rename operation updates **only the floor ID**    * Floor ownership, blocks, posts, and internal `fid` remain unchanged * Any links or references using the old floor ID may no longer be valid after rename  ---  ## Behavior Summary  | Scenario                     | Result                                            | | ---------------------------- | ------------------------------------------------- | | Valid owner + unique new ID  | Floor ID renamed successfully                     | | Non-owner user               | Request rejected                                  | | `from` floor ID not found    | Error                                             | | `to` floor ID already exists | Error                                             | | `from` == `to`               | No-op or validation error (implementation choice) |  ---  ## Response Format  `application/json`  ---  ## Sample Success Response  ```json {   \"status\": \"SUCCESS\",   \"old_floor_id\": \"oldfloorid\",   \"new_floor_id\": \"newfloorid\",   \"message\": \"Floor ID renamed successfully\" } ```  ---  ## Sample Error Responses  ### Not Floor Owner  ```json {   \"status\": \"ERROR\",   \"message\": \"Only the floor owner can rename the floor\" } ```  ---  ### Floor Not Found  ```json {   \"status\": \"ERROR\",   \"message\": \"Source floor ID does not exist\" } ```  ---  ### Floor ID Already Exists  ```json {   \"status\": \"ERROR\",   \"message\": \"Target floor ID is already in use\" } ```  ---  ### Invalid Request  ```json {   \"status\": \"ERROR\",   \"message\": \"user_id, from, and to are required\" } ```  ---  ## Notes for Developers  * This API **renames the public identifier only**; the internal immutable floor ID (`fid`) is not affected. * Clients should refresh cached floor metadata after a successful rename. * If your platform supports deep links or bookmarks, consider redirect or alias handling for old floor IDs (if supported).  ---  ### One-Line Mental Model  > **This API answers: “Change the public identity (ID) of a floor, owner-only.”** 
-     * @param {Object} opts Optional parameters
-     * @param {String} [userId] User ID
-     * @param {String} [appId] App ID
-     * @param {String} [from] Old floor ID
-     * @param {String} [to] New floor ID
+     * @param {String} userId User ID
+     * @param {String} appId App ID
+     * @param {String} from Old floor ID
+     * @param {String} to New floor ID
      * @param {module:api/DefaultApi~renameFloorCallback} callback The callback function, accepting three arguments: error, data, response
      * data is of type: {@link module:model/GetFloorInformation200Response}
      */
   }, {
     key: "renameFloor",
-    value: function renameFloor(opts, callback) {
-      opts = opts || {};
+    value: function renameFloor(userId, appId, from, to, callback) {
       var postBody = null;
+      // verify the required parameter 'userId' is set
+      if (userId === undefined || userId === null) {
+        throw new Error("Missing the required parameter 'userId' when calling renameFloor");
+      }
+      // verify the required parameter 'appId' is set
+      if (appId === undefined || appId === null) {
+        throw new Error("Missing the required parameter 'appId' when calling renameFloor");
+      }
+      // verify the required parameter 'from' is set
+      if (from === undefined || from === null) {
+        throw new Error("Missing the required parameter 'from' when calling renameFloor");
+      }
+      // verify the required parameter 'to' is set
+      if (to === undefined || to === null) {
+        throw new Error("Missing the required parameter 'to' when calling renameFloor");
+      }
       var pathParams = {};
       var queryParams = {
-        'user_id': opts['userId'],
-        'app_id': opts['appId'],
-        'from': opts['from'],
-        'to': opts['to']
+        'user_id': userId,
+        'app_id': appId,
+        'from': from,
+        'to': to
       };
       var headerParams = {};
       var formParams = {};
@@ -377,6 +574,48 @@ var DefaultApi = exports["default"] = /*#__PURE__*/function () {
       return this.apiClient.callApi('/auth-service/password/reset', 'POST', pathParams, queryParams, headerParams, formParams, postBody, authNames, contentTypes, accepts, returnType, null, callback);
     }
 
+    /**
+     * Callback function to receive the result of the sendSignInValidationCode operation.
+     * @callback module:api/DefaultApi~sendSignInValidationCodeCallback
+     * @param {String} error Error message, if any.
+     * @param {module:model/SendSignInValidationCode200Response} data The data returned by the service call.
+     * @param {String} response The complete HTTP response.
+     */
+
+    /**
+     * Send Sign-In Validation Code (OTP)
+     * This API initiates the **sign-in validation process** by sending a **one-time validation code (OTP)** to the user.  The OTP is delivered to **either the mobile number or the email address** provided in the request. This endpoint is typically called **before completing sign-in**, to verify that the user owns the supplied contact identifier.  The calling application is responsible for:  * Collecting the OTP from the user * Submitting it to the OTP verification API (handled separately)  ---  ## **Use Case**  * User attempts to sign in * User provides **mobile number or email** * System sends a **validation code (OTP)** * User enters OTP to complete sign-in  ---  ## **Request Method**  `POST`  ---  ## **Formdata Parameters**  | Parameter Name  | Type   | Required  | Description                                 | | --------------- | ------ | --------- | ------------------------------------------- | | `mobile_number` | String | Optional* | Mobile number to which the OTP will be sent | | `email_id`      | String | Optional* | Email address to which the OTP will be sent | | `app_id`        | String | Optional  | Identifier of the calling application       |  * **Either `mobile_number` or `email_id` must be provided.** Providing both is allowed; the system may choose one based on configuration.  ---  ## **Request Rules**  * At least **one** of `mobile_number` or `email_id` is mandatory * If both are missing, the request will be rejected * OTP delivery channel depends on the provided identifier  ---  ## **Response Format**  `application/json`  ---  ## **Sample Success Response**  ```json {   \"status\": \"SUCCESS\",   \"message\": \"Validation code sent successfully\" } ```  ---  ## **Sample Error Responses**  ### Missing Identifier  ```json {   \"status\": \"ERROR\",   \"message\": \"Either mobile_number or email_id must be provided\" } ```  ### Invalid Identifier  ```json {   \"status\": \"ERROR\",   \"message\": \"Invalid mobile number or email address\" } ```  ---  ## **Notes**  * This API **only sends** the validation code * OTP verification must be performed using the corresponding **verify validation code** API * Rate limiting and retry restrictions may apply to prevent abuse  
+     * @param {String} appId App ID
+     * @param {Object} opts Optional parameters
+     * @param {String} [mobileNumber] Mobile number
+     * @param {String} [emailId] Email ID
+     * @param {module:api/DefaultApi~sendSignInValidationCodeCallback} callback The callback function, accepting three arguments: error, data, response
+     * data is of type: {@link module:model/SendSignInValidationCode200Response}
+     */
+  }, {
+    key: "sendSignInValidationCode",
+    value: function sendSignInValidationCode(appId, opts, callback) {
+      opts = opts || {};
+      var postBody = null;
+      // verify the required parameter 'appId' is set
+      if (appId === undefined || appId === null) {
+        throw new Error("Missing the required parameter 'appId' when calling sendSignInValidationCode");
+      }
+      var pathParams = {};
+      var queryParams = {};
+      var headerParams = {};
+      var formParams = {
+        'mobile_number': opts['mobileNumber'],
+        'email_id': opts['emailId'],
+        'app_id': appId
+      };
+      var authNames = ['bearer'];
+      var contentTypes = ['multipart/form-data'];
+      var accepts = ['application/json'];
+      var returnType = _SendSignInValidationCode200Response["default"];
+      return this.apiClient.callApi('/auth-service/send/sign/in/validation/code', 'POST', pathParams, queryParams, headerParams, formParams, postBody, authNames, contentTypes, accepts, returnType, null, callback);
+    }
+
     /**
      * Callback function to receive the result of the sendValidationCode operation.
      * @callback module:api/DefaultApi~sendValidationCodeCallback

package/dist/api/EditFloorApi.js

@@ -15,7 +15,9 @@ function _createClass(e, r, t) { return r && _defineProperties(e.prototype, r),
 function _toPropertyKey(t) { var i = _toPrimitive(t, "string"); return "symbol" == _typeof(i) ? i : i + ""; }
 function _toPrimitive(t, r) { if ("object" != _typeof(t) || !t) return t; var e = t[Symbol.toPrimitive]; if (void 0 !== e) { var i = e.call(t, r || "default"); if ("object" != _typeof(i)) return i; throw new TypeError("@@toPrimitive must return a primitive value."); } return ("string" === r ? String : Number)(t); } /**
  * Floor Memory
- * The set APIs are used to develop Floor pds which can be used as their personal assistants.   This set of APIs are divided into two parts.  - Memory and  - Registration.   The developer has two ways of using the APIs for the app development. Developer can choose to the  Registration APIs for using the existing xfloor infracture or can implement custom Registration process. In the case of custom registration process, the developer is bound to provide proper authentication mechanisms and then send the user information to xlfoor.
+ * The set APIs are used to develop Floor pds which can be used as their personal assistants. This set of APIs are divided into two parts.
+ * - Memory and
+ * - Registration. The developer has two ways of using the APIs for the app development. Developer can choose to the Registration APIs for using the existing xfloor infracture or can implement custom Registration process. In the case of custom registration process, the developer is bound to provide proper authentication mechanisms and then send the user information to xlfoor.
  *
  * The version of the OpenAPI document: 1.0.0
  * Contact: contact@ipomo.in
@@ -28,7 +30,7 @@ function _toPrimitive(t, r) { if ("object" != _typeof(t) || !t) return t; var e
 /**
 * EditFloor service.
 * @module api/EditFloorApi
-* @version 1.0.4
+* @version 1.0.6
 */
 var EditFloorApi = exports["default"] = /*#__PURE__*/function () {
   /**

package/dist/api/EventApi.js

@@ -15,7 +15,9 @@ function _createClass(e, r, t) { return r && _defineProperties(e.prototype, r),
 function _toPropertyKey(t) { var i = _toPrimitive(t, "string"); return "symbol" == _typeof(i) ? i : i + ""; }
 function _toPrimitive(t, r) { if ("object" != _typeof(t) || !t) return t; var e = t[Symbol.toPrimitive]; if (void 0 !== e) { var i = e.call(t, r || "default"); if ("object" != _typeof(i)) return i; throw new TypeError("@@toPrimitive must return a primitive value."); } return ("string" === r ? String : Number)(t); } /**
  * Floor Memory
- * The set APIs are used to develop Floor pds which can be used as their personal assistants.   This set of APIs are divided into two parts.  - Memory and  - Registration.   The developer has two ways of using the APIs for the app development. Developer can choose to the  Registration APIs for using the existing xfloor infracture or can implement custom Registration process. In the case of custom registration process, the developer is bound to provide proper authentication mechanisms and then send the user information to xlfoor.
+ * The set APIs are used to develop Floor pds which can be used as their personal assistants. This set of APIs are divided into two parts.
+ * - Memory and
+ * - Registration. The developer has two ways of using the APIs for the app development. Developer can choose to the Registration APIs for using the existing xfloor infracture or can implement custom Registration process. In the case of custom registration process, the developer is bound to provide proper authentication mechanisms and then send the user information to xlfoor.
  *
  * The version of the OpenAPI document: 1.0.0
  * Contact: contact@ipomo.in
@@ -28,7 +30,7 @@ function _toPrimitive(t, r) { if ("object" != _typeof(t) || !t) return t; var e
 /**
 * Event service.
 * @module api/EventApi
-* @version 1.0.4
+* @version 1.0.6
 */
 var EventApi = exports["default"] = /*#__PURE__*/function () {
   /**
@@ -53,7 +55,7 @@ var EventApi = exports["default"] = /*#__PURE__*/function () {
 
   /**
    * Create Event (Post Content)
-   * Posts into the given floor_id. This is asynchronous ingestion. 200 OK means queued, not immediately retrievable. This API allows a user to **post personal content into their POD (Personal Object Database)**. The posted content is stored under a specified **floor**, embedded by the platform, and made available for **semantic querying, conversational retrieval, and memory-based interactions**.  It is primarily used to:  * Save reminders, notes, writeups, or personal knowledge * Upload content that the user wants the system to remember * Add information that should later be discoverable via conversational queries  The content may consist of **text only** or **text combined with one or more media files**.  ---  ## **Key Capabilities**  * Stores user-generated content inside a specific floor * Supports **multi-modal inputs** (text + media) * Automatically embeds content for semantic search * Makes content available to:    * `/agent/memory/query`   * conversational agents   * future recall and analytics * Associates content with user, block, and application context  ---  ## **Authentication**  * Requires a valid, authenticated `user_id` * The calling application is responsible for user authentication * `app_id` identifies the application context  ---  ## **Request Type**  **Content-Type:** `multipart/form-data`  ---  ## **Request Parameters**  ### **1. Files (Optional)**  | Field   | Type   | Required | Description                                                           | | ------- | ------ | -------- | --------------------------------------------------------------------- | | `files` | file[] | Optional | Media files to attach to the content. Multiple files may be uploaded. |  **Supported formats include (but are not limited to):**  * Images: `jpg`, `png` * Audio: `mp3` * Documents: `pdf` * Video: `mp4`  These files are processed and embedded along with the textual content where applicable.  ---  ### **2. Input Information (Required)**  | Field        | Type          | Required | Description                                                       | | ------------ | ------------- | -------- | ----------------------------------------------------------------- | | `input_info` | string (JSON) | Yes      | JSON string containing metadata and textual content for the post. |  ---  ## **`input_info` Structure**  ```json {   \"floor_id\": \"my_floor\",   \"BID\": \"17845683456\",   \"user_id\": \"145623907625\",   \"title\": \"My floor\",   \"description\": \"My floor details\",   \"app_id\": \"165434879028\" } ```  ---  ### **Field Descriptions**  | Field         | Type   | Required | Description                                                                        | | ------------- | ------ | -------- | ---------------------------------------------------------------------------------- | | `floor_id`    | string | Yes      | Identifier of the user’s floor (POD) where the content will be stored.             | | `block_type`  | string | Yes      | Type of block under which the content is categorized (e.g., post, note, reminder). | | `BID`         | string | Yes      | Block identifier associated with this content.                                     | | `user_id`     | string | Yes      | Unique identifier of the user posting the content.                                 | | `title`       | string | Optional | Title or short heading for the content.                                            | | `description` | string | Yes      | Main textual content to be stored and embedded.                                    | | `app_id`      | string | Optional | Identifier of the calling application.                                             |  ---  ## **Behavior**  1. The API validates the user and floor context. 2. Textual content (`title` and `description`) is ingested. 3. Attached media files are processed and linked to the content. 4. Embeddings are generated for:     * Text    * Supported media (where applicable) 5. The content becomes part of the user’s **personal memory store**. 6. The stored data is immediately available for querying and conversational retrieval.  ---  ## **Successful Response**  On success, the API confirms that:  * The content has been stored * Embeddings have been generated * The memory item is available for future queries  A success status and reference identifiers are returned.  ---  ## **Error Handling**  The API may return errors if:  * Required fields are missing (`floor_id`, `user_id`, `description`) * Unsupported file formats are uploaded * The user does not have access to the specified floor * The request payload is malformed * Internal embedding or storage operations fail  ---  ## **Typical Use Cases**  * Saving personal reminders * Posting notes or observations * Uploading documents for future reference * Creating a personal knowledge base * Feeding data into conversational agents  ---  ## **One-Line Summary**  > Stores user-generated text and media into a personal POD, embeds it for semantic search, and makes it available for conversational querying.  ⚠️ Content Ingestion is Asynchronous  The Create Event API queues content for processing. A successful response indicates **acceptance**, not availability.  Newly ingested content may take time to become searchable via the Query API.  
+   * ## Create Event (Content Ingestion)  Posts content into the specified `floor_id`. This API performs **asynchronous ingestion** — a `200 OK` response means the content has been **accepted and queued**, not immediately retrievable.  This API allows a user to **post personal content into their POD (Personal Object Database)**.  The posted content is stored under a specified **floor**, embedded by the platform, and made available for **semantic querying, conversational retrieval, and memory-based interactions** once processing completes.  It is primarily used to:  * Save reminders, notes, write-ups, or personal knowledge * Upload content the user wants the system to remember * Add information that should later be discoverable via conversational queries  The content may consist of **text only** or **text combined with one or more media files**.  ---  ## Key Capabilities  * Stores user-generated content inside a specific floor * Supports **multi-modal inputs** (text + media) * Automatically embeds content for semantic search * Makes content available to:    * `/agent/memory/query`   * conversational agents   * future recall and analytics * Associates content with **user**, **block**, and **application** context (when provided)  ---  ## Authentication  * Requires a valid, authenticated `user_id` * The calling application is responsible for user authentication * `app_id` identifies the application context  ---  ## Request Type  **Content-Type:** `multipart/form-data`  ---  ## Request Parameters  ### 1. Files (Optional)  | Field   | Type     | Required | Description                                                           | | ------- | -------- | -------- | --------------------------------------------------------------------- | | `files` | `file[]` | Optional | Media files to attach to the content. Multiple files may be uploaded. |  **Supported formats include (but are not limited to):**  * Images: `jpg`, `png` * Audio: `mp3` * Documents: `pdf` * Video: `mp4`  These files are processed and embedded along with the textual content where applicable.  ---  ### 2. Input Information (Required)  | Field        | Type            | Required | Description                                                       | | ------------ | --------------- | -------- | ----------------------------------------------------------------- | | `input_info` | `string (JSON)` | Yes      | JSON string containing metadata and textual content for the post. |  ---  ## `input_info` Structure  ```json {   \"floor_id\": \"my_floor\",   \"block_id\": \"17845683456\",   \"block_type\": \"post\",   \"user_id\": \"145623907625\",   \"title\": \"My note\",   \"description\": \"Things I should remember\",   \"app_id\": \"165434879028\" } ```  ---  ## Field Descriptions  | Field         | Type     | Required | Description                                                                                               | | ------------- | -------- | -------- | --------------------------------------------------------------------------------------------------------- | | `floor_id`    | `string` | Yes      | Identifier of the user’s floor (POD) where the content will be stored.                                    | | `block_id`    | `string` | Optional | Identifier of the block within the floor used to group or categorize content.                             | | `block_type`  | `string` | Optional | Logical category of the content (e.g., `post`, `note`, `reminder`). Used for routing and UI organization. | | `user_id`     | `string` | Yes      | Unique identifier of the user posting the content.                                                        | | `title`       | `string` | Optional | Short title or heading for the content.                                                                   | | `description` | `string` | Yes      | Main textual content to be stored and embedded.                                                           | | `app_id`      | `string` | Optional | Identifier of the calling application context.                                                            |  ---  ## Behavior  1. The API validates the user and floor context. 2. Textual content (`title` and `description`) is ingested. 3. Attached media files (if any) are processed and linked to the content. 4. Embeddings are generated for:     * text    * supported media (where applicable) 5. The content becomes part of the user’s **personal memory store (POD)**. 6. Once background processing completes, the content becomes available for:     * semantic search    * conversational retrieval    * memory-based interactions  ---  ## Successful Response  On success, the API confirms that:  * The content has been **accepted** * Processing has been **queued** * Reference identifiers are returned  > A successful response indicates **acceptance**, not immediate availability.  ---  ## Error Handling  The API may return errors if:  * Required fields are missing (`floor_id`, `user_id`, `description`) * Uploaded files use unsupported formats * The user does not have access to the specified floor * The request payload is malformed * Internal embedding or storage operations fail  ---  ## Typical Use Cases  * Saving personal reminders * Posting notes or observations * Uploading documents for later recall * Building a personal knowledge base * Feeding content into conversational agents  ---  ## ⚠️ Asynchronous Ingestion Notice  Content ingestion is **asynchronous**.  A `200 OK` response means the request was **successfully queued**. Newly ingested content may take time to become searchable via the Query API.  Use **Recent Events** or retry queries after a short delay to confirm availability.  ---  ## One-Line Summary  > Stores user-generated text and media into a personal POD, embeds it asynchronously, and makes it available for semantic and conversational querying.  If you want, next I can:  * align this **exactly** with the OpenAPI schema fields * generate **JS / TS / Python / Java snippets** using this definition * add **state diagrams** (queued → processing → searchable) for docs 
    * @param {String} inputInfo Input parameters, bid is optional
    * @param {Object} opts Optional parameters
    * @param {File} [files] Attach relevant media here, which includes, jpg, mp3, pdf, mp4 files. More than one media can be selected