@xfloor/floor-memory-sdk-ts 1.0.0

package/dist/apis/EditFloorApi.d.ts

@@ -0,0 +1,36 @@
+/**
+ * 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 version of the OpenAPI document: 1.0.0
+ * Contact: contact@ipomo.in
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+import * as runtime from '../runtime';
+import type { GetFloorInformation200Response } from '../models/index';
+export interface EditFloorRequest {
+    floorId: string;
+    userId: string;
+    appId: string;
+    logoFile?: Blob;
+    title?: string;
+    details?: string;
+}
+/**
+ *
+ */
+export declare class EditFloorApi extends runtime.BaseAPI {
+    /**
+     * This API updates an existing floor’s profile metadata using **multipart form data**.  A floor **can be edited only by its owner**. If the authenticated user is **not the owner of the floor**, the request will be rejected, even if the user is a member or follower of the floor.  The API allows the floor owner to update:  * Floor **title** * Floor **details/description** * Floor **logo/avatar image**  After a successful update, the API returns the **latest floor object**, including the updated avatar and the current list of blocks associated with the floor.  ---  ## Authorization Rules (Critical)  * The caller **must be authenticated** * The caller **must be the owner of the floor** * Members, followers, or pod consumers **cannot** edit the floor * Ownership is validated internally using the authenticated user context  > **Ownership is mandatory. There are no partial permissions for this API.**  ---  ## Content-Type  `multipart/form-data`  ---  ## Request Body (Multipart Form Data)  ### Form Fields  | Field Name | Type   | Required     | Description                              | | ---------- | ------ | ------------ | ---------------------------------------- | | `fid`      | String | Recommended* | Immutable internal floor ID              | | `floor_id` | String | Optional*    | Public / human-readable floor identifier | | `title`    | String | Optional     | New floor title                          | | `details`  | String | Optional     | New floor description                    | | `logo`     | File   | Optional     | New floor logo image (PNG/JPG/WebP)      |  * At least **one floor identifier** (`fid` or `floor_id`) must be provided. **Best practice:** Use `fid` as the primary identifier.  ---  ## Update Rules  * At least one of `title`, `details`, or `logo` must be present * Missing update fields result in a validation error * If `logo` is provided, the previous logo is replaced  ---  ## Response Format  `application/json`  ---  ## Sample Success Response  ```json {   \"floor_id\": \"my_floor\",   \"title\": \"daughter ouch upon yummy clamor\",   \"details\": \"nostrud occaecat incididunt dolor adipisicing\",   \"fid\": \"86\",   \"blocks\": [     {       \"bid\": \"83\",       \"type\": \"pariatur\",       \"title\": \"wherever demobilise acidly refute\"     }   ],   \"avatar\": {     \"url\": \"https://legal-availability.name/\",     \"id\": \"98\"   } } ```  ---  ## Error Responses (Authorization Focus)  ### Not Floor Owner  ```json {   \"status\": \"ERROR\",   \"message\": \"Only the floor owner can edit this floor\" } ```  ### Floor Not Found  ```json {   \"status\": \"ERROR\",   \"message\": \"Floor not found\" } ```  ### No Update Fields  ```json {   \"status\": \"ERROR\",   \"message\": \"No update fields provided\" } ```  ---  ## Notes  * This API is **owner-only by design** * Pods and developer tools must operate using **owner credentials** * Blocks are returned for convenience but are **not editable through this API**  ---
+     * Edit floor
+     */
+    editFloorRaw(requestParameters: EditFloorRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<GetFloorInformation200Response>>;
+    /**
+     * This API updates an existing floor’s profile metadata using **multipart form data**.  A floor **can be edited only by its owner**. If the authenticated user is **not the owner of the floor**, the request will be rejected, even if the user is a member or follower of the floor.  The API allows the floor owner to update:  * Floor **title** * Floor **details/description** * Floor **logo/avatar image**  After a successful update, the API returns the **latest floor object**, including the updated avatar and the current list of blocks associated with the floor.  ---  ## Authorization Rules (Critical)  * The caller **must be authenticated** * The caller **must be the owner of the floor** * Members, followers, or pod consumers **cannot** edit the floor * Ownership is validated internally using the authenticated user context  > **Ownership is mandatory. There are no partial permissions for this API.**  ---  ## Content-Type  `multipart/form-data`  ---  ## Request Body (Multipart Form Data)  ### Form Fields  | Field Name | Type   | Required     | Description                              | | ---------- | ------ | ------------ | ---------------------------------------- | | `fid`      | String | Recommended* | Immutable internal floor ID              | | `floor_id` | String | Optional*    | Public / human-readable floor identifier | | `title`    | String | Optional     | New floor title                          | | `details`  | String | Optional     | New floor description                    | | `logo`     | File   | Optional     | New floor logo image (PNG/JPG/WebP)      |  * At least **one floor identifier** (`fid` or `floor_id`) must be provided. **Best practice:** Use `fid` as the primary identifier.  ---  ## Update Rules  * At least one of `title`, `details`, or `logo` must be present * Missing update fields result in a validation error * If `logo` is provided, the previous logo is replaced  ---  ## Response Format  `application/json`  ---  ## Sample Success Response  ```json {   \"floor_id\": \"my_floor\",   \"title\": \"daughter ouch upon yummy clamor\",   \"details\": \"nostrud occaecat incididunt dolor adipisicing\",   \"fid\": \"86\",   \"blocks\": [     {       \"bid\": \"83\",       \"type\": \"pariatur\",       \"title\": \"wherever demobilise acidly refute\"     }   ],   \"avatar\": {     \"url\": \"https://legal-availability.name/\",     \"id\": \"98\"   } } ```  ---  ## Error Responses (Authorization Focus)  ### Not Floor Owner  ```json {   \"status\": \"ERROR\",   \"message\": \"Only the floor owner can edit this floor\" } ```  ### Floor Not Found  ```json {   \"status\": \"ERROR\",   \"message\": \"Floor not found\" } ```  ### No Update Fields  ```json {   \"status\": \"ERROR\",   \"message\": \"No update fields provided\" } ```  ---  ## Notes  * This API is **owner-only by design** * Pods and developer tools must operate using **owner credentials** * Blocks are returned for convenience but are **not editable through this API**  ---
+     * Edit floor
+     */
+    editFloor(requestParameters: EditFloorRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<GetFloorInformation200Response>;
+}

package/dist/apis/EditFloorApi.js

@@ -0,0 +1,173 @@
+"use strict";
+/* tslint:disable */
+/* eslint-disable */
+/**
+ * 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 version of the OpenAPI document: 1.0.0
+ * Contact: contact@ipomo.in
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+var __extends = (this && this.__extends) || (function () {
+    var extendStatics = function (d, b) {
+        extendStatics = Object.setPrototypeOf ||
+            ({ __proto__: [] } instanceof Array && function (d, b) { d.__proto__ = b; }) ||
+            function (d, b) { for (var p in b) if (Object.prototype.hasOwnProperty.call(b, p)) d[p] = b[p]; };
+        return extendStatics(d, b);
+    };
+    return function (d, b) {
+        if (typeof b !== "function" && b !== null)
+            throw new TypeError("Class extends value " + String(b) + " is not a constructor or null");
+        extendStatics(d, b);
+        function __() { this.constructor = d; }
+        d.prototype = b === null ? Object.create(b) : (__.prototype = b.prototype, new __());
+    };
+})();
+var __awaiter = (this && this.__awaiter) || function (thisArg, _arguments, P, generator) {
+    function adopt(value) { return value instanceof P ? value : new P(function (resolve) { resolve(value); }); }
+    return new (P || (P = Promise))(function (resolve, reject) {
+        function fulfilled(value) { try { step(generator.next(value)); } catch (e) { reject(e); } }
+        function rejected(value) { try { step(generator["throw"](value)); } catch (e) { reject(e); } }
+        function step(result) { result.done ? resolve(result.value) : adopt(result.value).then(fulfilled, rejected); }
+        step((generator = generator.apply(thisArg, _arguments || [])).next());
+    });
+};
+var __generator = (this && this.__generator) || function (thisArg, body) {
+    var _ = { label: 0, sent: function() { if (t[0] & 1) throw t[1]; return t[1]; }, trys: [], ops: [] }, f, y, t, g = Object.create((typeof Iterator === "function" ? Iterator : Object).prototype);
+    return g.next = verb(0), g["throw"] = verb(1), g["return"] = verb(2), typeof Symbol === "function" && (g[Symbol.iterator] = function() { return this; }), g;
+    function verb(n) { return function (v) { return step([n, v]); }; }
+    function step(op) {
+        if (f) throw new TypeError("Generator is already executing.");
+        while (g && (g = 0, op[0] && (_ = 0)), _) try {
+            if (f = 1, y && (t = op[0] & 2 ? y["return"] : op[0] ? y["throw"] || ((t = y["return"]) && t.call(y), 0) : y.next) && !(t = t.call(y, op[1])).done) return t;
+            if (y = 0, t) op = [op[0] & 2, t.value];
+            switch (op[0]) {
+                case 0: case 1: t = op; break;
+                case 4: _.label++; return { value: op[1], done: false };
+                case 5: _.label++; y = op[1]; op = [0]; continue;
+                case 7: op = _.ops.pop(); _.trys.pop(); continue;
+                default:
+                    if (!(t = _.trys, t = t.length > 0 && t[t.length - 1]) && (op[0] === 6 || op[0] === 2)) { _ = 0; continue; }
+                    if (op[0] === 3 && (!t || (op[1] > t[0] && op[1] < t[3]))) { _.label = op[1]; break; }
+                    if (op[0] === 6 && _.label < t[1]) { _.label = t[1]; t = op; break; }
+                    if (t && _.label < t[2]) { _.label = t[2]; _.ops.push(op); break; }
+                    if (t[2]) _.ops.pop();
+                    _.trys.pop(); continue;
+            }
+            op = body.call(thisArg, _);
+        } catch (e) { op = [6, e]; y = 0; } finally { f = t = 0; }
+        if (op[0] & 5) throw op[1]; return { value: op[0] ? op[1] : void 0, done: true };
+    }
+};
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.EditFloorApi = void 0;
+var runtime = require("../runtime");
+var index_1 = require("../models/index");
+/**
+ *
+ */
+var EditFloorApi = /** @class */ (function (_super) {
+    __extends(EditFloorApi, _super);
+    function EditFloorApi() {
+        return _super !== null && _super.apply(this, arguments) || this;
+    }
+    /**
+     * This API updates an existing floor’s profile metadata using **multipart form data**.  A floor **can be edited only by its owner**. If the authenticated user is **not the owner of the floor**, the request will be rejected, even if the user is a member or follower of the floor.  The API allows the floor owner to update:  * Floor **title** * Floor **details/description** * Floor **logo/avatar image**  After a successful update, the API returns the **latest floor object**, including the updated avatar and the current list of blocks associated with the floor.  ---  ## Authorization Rules (Critical)  * The caller **must be authenticated** * The caller **must be the owner of the floor** * Members, followers, or pod consumers **cannot** edit the floor * Ownership is validated internally using the authenticated user context  > **Ownership is mandatory. There are no partial permissions for this API.**  ---  ## Content-Type  `multipart/form-data`  ---  ## Request Body (Multipart Form Data)  ### Form Fields  | Field Name | Type   | Required     | Description                              | | ---------- | ------ | ------------ | ---------------------------------------- | | `fid`      | String | Recommended* | Immutable internal floor ID              | | `floor_id` | String | Optional*    | Public / human-readable floor identifier | | `title`    | String | Optional     | New floor title                          | | `details`  | String | Optional     | New floor description                    | | `logo`     | File   | Optional     | New floor logo image (PNG/JPG/WebP)      |  * At least **one floor identifier** (`fid` or `floor_id`) must be provided. **Best practice:** Use `fid` as the primary identifier.  ---  ## Update Rules  * At least one of `title`, `details`, or `logo` must be present * Missing update fields result in a validation error * If `logo` is provided, the previous logo is replaced  ---  ## Response Format  `application/json`  ---  ## Sample Success Response  ```json {   \"floor_id\": \"my_floor\",   \"title\": \"daughter ouch upon yummy clamor\",   \"details\": \"nostrud occaecat incididunt dolor adipisicing\",   \"fid\": \"86\",   \"blocks\": [     {       \"bid\": \"83\",       \"type\": \"pariatur\",       \"title\": \"wherever demobilise acidly refute\"     }   ],   \"avatar\": {     \"url\": \"https://legal-availability.name/\",     \"id\": \"98\"   } } ```  ---  ## Error Responses (Authorization Focus)  ### Not Floor Owner  ```json {   \"status\": \"ERROR\",   \"message\": \"Only the floor owner can edit this floor\" } ```  ### Floor Not Found  ```json {   \"status\": \"ERROR\",   \"message\": \"Floor not found\" } ```  ### No Update Fields  ```json {   \"status\": \"ERROR\",   \"message\": \"No update fields provided\" } ```  ---  ## Notes  * This API is **owner-only by design** * Pods and developer tools must operate using **owner credentials** * Blocks are returned for convenience but are **not editable through this API**  ---
+     * Edit floor
+     */
+    EditFloorApi.prototype.editFloorRaw = function (requestParameters, initOverrides) {
+        return __awaiter(this, void 0, void 0, function () {
+            var queryParameters, headerParameters, token, tokenString, consumes, canConsumeForm, formParams, useForm, urlPath, response;
+            return __generator(this, function (_a) {
+                switch (_a.label) {
+                    case 0:
+                        if (requestParameters['floorId'] == null) {
+                            throw new runtime.RequiredError('floorId', 'Required parameter "floorId" was null or undefined when calling editFloor().');
+                        }
+                        if (requestParameters['userId'] == null) {
+                            throw new runtime.RequiredError('userId', 'Required parameter "userId" was null or undefined when calling editFloor().');
+                        }
+                        if (requestParameters['appId'] == null) {
+                            throw new runtime.RequiredError('appId', 'Required parameter "appId" was null or undefined when calling editFloor().');
+                        }
+                        queryParameters = {};
+                        headerParameters = {};
+                        if (!(this.configuration && this.configuration.accessToken)) return [3 /*break*/, 2];
+                        token = this.configuration.accessToken;
+                        return [4 /*yield*/, token("bearer", [])];
+                    case 1:
+                        tokenString = _a.sent();
+                        if (tokenString) {
+                            headerParameters["Authorization"] = "Bearer ".concat(tokenString);
+                        }
+                        _a.label = 2;
+                    case 2:
+                        consumes = [
+                            { contentType: 'multipart/form-data' },
+                        ];
+                        canConsumeForm = runtime.canConsumeForm(consumes);
+                        useForm = false;
+                        // use FormData to transmit files using content-type "multipart/form-data"
+                        useForm = canConsumeForm;
+                        if (useForm) {
+                            formParams = new FormData();
+                        }
+                        else {
+                            formParams = new URLSearchParams();
+                        }
+                        if (requestParameters['userId'] != null) {
+                            formParams.append('user_id', requestParameters['userId']);
+                        }
+                        if (requestParameters['appId'] != null) {
+                            formParams.append('app_id', requestParameters['appId']);
+                        }
+                        if (requestParameters['logoFile'] != null) {
+                            formParams.append('logo_file', requestParameters['logoFile']);
+                        }
+                        if (requestParameters['title'] != null) {
+                            formParams.append('title', requestParameters['title']);
+                        }
+                        if (requestParameters['details'] != null) {
+                            formParams.append('details', requestParameters['details']);
+                        }
+                        urlPath = "/api/memory/edit/floor/{floor_id}";
+                        urlPath = urlPath.replace("{".concat("floor_id", "}"), encodeURIComponent(String(requestParameters['floorId'])));
+                        return [4 /*yield*/, this.request({
+                                path: urlPath,
+                                method: 'POST',
+                                headers: headerParameters,
+                                query: queryParameters,
+                                body: formParams,
+                            }, initOverrides)];
+                    case 3:
+                        response = _a.sent();
+                        return [2 /*return*/, new runtime.JSONApiResponse(response, function (jsonValue) { return (0, index_1.GetFloorInformation200ResponseFromJSON)(jsonValue); })];
+                }
+            });
+        });
+    };
+    /**
+     * This API updates an existing floor’s profile metadata using **multipart form data**.  A floor **can be edited only by its owner**. If the authenticated user is **not the owner of the floor**, the request will be rejected, even if the user is a member or follower of the floor.  The API allows the floor owner to update:  * Floor **title** * Floor **details/description** * Floor **logo/avatar image**  After a successful update, the API returns the **latest floor object**, including the updated avatar and the current list of blocks associated with the floor.  ---  ## Authorization Rules (Critical)  * The caller **must be authenticated** * The caller **must be the owner of the floor** * Members, followers, or pod consumers **cannot** edit the floor * Ownership is validated internally using the authenticated user context  > **Ownership is mandatory. There are no partial permissions for this API.**  ---  ## Content-Type  `multipart/form-data`  ---  ## Request Body (Multipart Form Data)  ### Form Fields  | Field Name | Type   | Required     | Description                              | | ---------- | ------ | ------------ | ---------------------------------------- | | `fid`      | String | Recommended* | Immutable internal floor ID              | | `floor_id` | String | Optional*    | Public / human-readable floor identifier | | `title`    | String | Optional     | New floor title                          | | `details`  | String | Optional     | New floor description                    | | `logo`     | File   | Optional     | New floor logo image (PNG/JPG/WebP)      |  * At least **one floor identifier** (`fid` or `floor_id`) must be provided. **Best practice:** Use `fid` as the primary identifier.  ---  ## Update Rules  * At least one of `title`, `details`, or `logo` must be present * Missing update fields result in a validation error * If `logo` is provided, the previous logo is replaced  ---  ## Response Format  `application/json`  ---  ## Sample Success Response  ```json {   \"floor_id\": \"my_floor\",   \"title\": \"daughter ouch upon yummy clamor\",   \"details\": \"nostrud occaecat incididunt dolor adipisicing\",   \"fid\": \"86\",   \"blocks\": [     {       \"bid\": \"83\",       \"type\": \"pariatur\",       \"title\": \"wherever demobilise acidly refute\"     }   ],   \"avatar\": {     \"url\": \"https://legal-availability.name/\",     \"id\": \"98\"   } } ```  ---  ## Error Responses (Authorization Focus)  ### Not Floor Owner  ```json {   \"status\": \"ERROR\",   \"message\": \"Only the floor owner can edit this floor\" } ```  ### Floor Not Found  ```json {   \"status\": \"ERROR\",   \"message\": \"Floor not found\" } ```  ### No Update Fields  ```json {   \"status\": \"ERROR\",   \"message\": \"No update fields provided\" } ```  ---  ## Notes  * This API is **owner-only by design** * Pods and developer tools must operate using **owner credentials** * Blocks are returned for convenience but are **not editable through this API**  ---
+     * Edit floor
+     */
+    EditFloorApi.prototype.editFloor = function (requestParameters, initOverrides) {
+        return __awaiter(this, void 0, void 0, function () {
+            var response;
+            return __generator(this, function (_a) {
+                switch (_a.label) {
+                    case 0: return [4 /*yield*/, this.editFloorRaw(requestParameters, initOverrides)];
+                    case 1:
+                        response = _a.sent();
+                        return [4 /*yield*/, response.value()];
+                    case 2: return [2 /*return*/, _a.sent()];
+                }
+            });
+        });
+    };
+    return EditFloorApi;
+}(runtime.BaseAPI));
+exports.EditFloorApi = EditFloorApi;

package/dist/apis/EventApi.d.ts

@@ -0,0 +1,32 @@
+/**
+ * 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 version of the OpenAPI document: 1.0.0
+ * Contact: contact@ipomo.in
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+import * as runtime from '../runtime';
+import type { EventResponse } from '../models/index';
+export interface EventRequest {
+    inputInfo: string;
+    files?: Blob;
+}
+/**
+ *
+ */
+export declare class EventApi extends runtime.BaseAPI {
+    /**
+     * 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 (Post Content)
+     */
+    eventRaw(requestParameters: EventRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<EventResponse>>;
+    /**
+     * 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 (Post Content)
+     */
+    event(requestParameters: EventRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<EventResponse>;
+}

package/dist/apis/EventApi.js

@@ -0,0 +1,157 @@
+"use strict";
+/* tslint:disable */
+/* eslint-disable */
+/**
+ * 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 version of the OpenAPI document: 1.0.0
+ * Contact: contact@ipomo.in
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+var __extends = (this && this.__extends) || (function () {
+    var extendStatics = function (d, b) {
+        extendStatics = Object.setPrototypeOf ||
+            ({ __proto__: [] } instanceof Array && function (d, b) { d.__proto__ = b; }) ||
+            function (d, b) { for (var p in b) if (Object.prototype.hasOwnProperty.call(b, p)) d[p] = b[p]; };
+        return extendStatics(d, b);
+    };
+    return function (d, b) {
+        if (typeof b !== "function" && b !== null)
+            throw new TypeError("Class extends value " + String(b) + " is not a constructor or null");
+        extendStatics(d, b);
+        function __() { this.constructor = d; }
+        d.prototype = b === null ? Object.create(b) : (__.prototype = b.prototype, new __());
+    };
+})();
+var __awaiter = (this && this.__awaiter) || function (thisArg, _arguments, P, generator) {
+    function adopt(value) { return value instanceof P ? value : new P(function (resolve) { resolve(value); }); }
+    return new (P || (P = Promise))(function (resolve, reject) {
+        function fulfilled(value) { try { step(generator.next(value)); } catch (e) { reject(e); } }
+        function rejected(value) { try { step(generator["throw"](value)); } catch (e) { reject(e); } }
+        function step(result) { result.done ? resolve(result.value) : adopt(result.value).then(fulfilled, rejected); }
+        step((generator = generator.apply(thisArg, _arguments || [])).next());
+    });
+};
+var __generator = (this && this.__generator) || function (thisArg, body) {
+    var _ = { label: 0, sent: function() { if (t[0] & 1) throw t[1]; return t[1]; }, trys: [], ops: [] }, f, y, t, g = Object.create((typeof Iterator === "function" ? Iterator : Object).prototype);
+    return g.next = verb(0), g["throw"] = verb(1), g["return"] = verb(2), typeof Symbol === "function" && (g[Symbol.iterator] = function() { return this; }), g;
+    function verb(n) { return function (v) { return step([n, v]); }; }
+    function step(op) {
+        if (f) throw new TypeError("Generator is already executing.");
+        while (g && (g = 0, op[0] && (_ = 0)), _) try {
+            if (f = 1, y && (t = op[0] & 2 ? y["return"] : op[0] ? y["throw"] || ((t = y["return"]) && t.call(y), 0) : y.next) && !(t = t.call(y, op[1])).done) return t;
+            if (y = 0, t) op = [op[0] & 2, t.value];
+            switch (op[0]) {
+                case 0: case 1: t = op; break;
+                case 4: _.label++; return { value: op[1], done: false };
+                case 5: _.label++; y = op[1]; op = [0]; continue;
+                case 7: op = _.ops.pop(); _.trys.pop(); continue;
+                default:
+                    if (!(t = _.trys, t = t.length > 0 && t[t.length - 1]) && (op[0] === 6 || op[0] === 2)) { _ = 0; continue; }
+                    if (op[0] === 3 && (!t || (op[1] > t[0] && op[1] < t[3]))) { _.label = op[1]; break; }
+                    if (op[0] === 6 && _.label < t[1]) { _.label = t[1]; t = op; break; }
+                    if (t && _.label < t[2]) { _.label = t[2]; _.ops.push(op); break; }
+                    if (t[2]) _.ops.pop();
+                    _.trys.pop(); continue;
+            }
+            op = body.call(thisArg, _);
+        } catch (e) { op = [6, e]; y = 0; } finally { f = t = 0; }
+        if (op[0] & 5) throw op[1]; return { value: op[0] ? op[1] : void 0, done: true };
+    }
+};
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.EventApi = void 0;
+var runtime = require("../runtime");
+var index_1 = require("../models/index");
+/**
+ *
+ */
+var EventApi = /** @class */ (function (_super) {
+    __extends(EventApi, _super);
+    function EventApi() {
+        return _super !== null && _super.apply(this, arguments) || this;
+    }
+    /**
+     * 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 (Post Content)
+     */
+    EventApi.prototype.eventRaw = function (requestParameters, initOverrides) {
+        return __awaiter(this, void 0, void 0, function () {
+            var queryParameters, headerParameters, token, tokenString, consumes, canConsumeForm, formParams, useForm, urlPath, response;
+            return __generator(this, function (_a) {
+                switch (_a.label) {
+                    case 0:
+                        if (requestParameters['inputInfo'] == null) {
+                            throw new runtime.RequiredError('inputInfo', 'Required parameter "inputInfo" was null or undefined when calling event().');
+                        }
+                        queryParameters = {};
+                        headerParameters = {};
+                        if (!(this.configuration && this.configuration.accessToken)) return [3 /*break*/, 2];
+                        token = this.configuration.accessToken;
+                        return [4 /*yield*/, token("bearer", [])];
+                    case 1:
+                        tokenString = _a.sent();
+                        if (tokenString) {
+                            headerParameters["Authorization"] = "Bearer ".concat(tokenString);
+                        }
+                        _a.label = 2;
+                    case 2:
+                        consumes = [
+                            { contentType: 'multipart/form-data' },
+                        ];
+                        canConsumeForm = runtime.canConsumeForm(consumes);
+                        useForm = false;
+                        // use FormData to transmit files using content-type "multipart/form-data"
+                        useForm = canConsumeForm;
+                        if (useForm) {
+                            formParams = new FormData();
+                        }
+                        else {
+                            formParams = new URLSearchParams();
+                        }
+                        if (requestParameters['files'] != null) {
+                            formParams.append('files', requestParameters['files']);
+                        }
+                        if (requestParameters['inputInfo'] != null) {
+                            formParams.append('input_info', requestParameters['inputInfo']);
+                        }
+                        urlPath = "/api/memory/events";
+                        return [4 /*yield*/, this.request({
+                                path: urlPath,
+                                method: 'POST',
+                                headers: headerParameters,
+                                query: queryParameters,
+                                body: formParams,
+                            }, initOverrides)];
+                    case 3:
+                        response = _a.sent();
+                        return [2 /*return*/, new runtime.JSONApiResponse(response, function (jsonValue) { return (0, index_1.EventResponseFromJSON)(jsonValue); })];
+                }
+            });
+        });
+    };
+    /**
+     * 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 (Post Content)
+     */
+    EventApi.prototype.event = function (requestParameters, initOverrides) {
+        return __awaiter(this, void 0, void 0, function () {
+            var response;
+            return __generator(this, function (_a) {
+                switch (_a.label) {
+                    case 0: return [4 /*yield*/, this.eventRaw(requestParameters, initOverrides)];
+                    case 1:
+                        response = _a.sent();
+                        return [4 /*yield*/, response.value()];
+                    case 2: return [2 /*return*/, _a.sent()];
+                }
+            });
+        });
+    };
+    return EventApi;
+}(runtime.BaseAPI));
+exports.EventApi = EventApi;

package/dist/apis/GetFloorInformationApi.d.ts

@@ -0,0 +1,33 @@
+/**
+ * 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 version of the OpenAPI document: 1.0.0
+ * Contact: contact@ipomo.in
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+import * as runtime from '../runtime';
+import type { GetFloorInformation200Response } from '../models/index';
+export interface GetFloorInformationRequest {
+    floorId: string;
+    userId?: string;
+    appId?: string;
+}
+/**
+ *
+ */
+export declare class GetFloorInformationApi extends runtime.BaseAPI {
+    /**
+     * This API returns the **basic profile information of a floor**. It is used to fetch all essential metadata required to **render a floor landing page, header, or navigation context**.  The response includes:  * Floor identity and type * Ownership information relative to the requesting user * Floor metadata (title, description, avatar) * List of blocks available in the floor * App association (for pod / developer use cases)  This API does **not** return posts or content; it only provides **structural and descriptive information** about the floor.  ---  ## Typical Use Cases  * Render floor header (title, logo, description) * Decide UI permissions (owner vs non-owner) * Display available blocks (Feeds, Blog, Quiz, etc.) * Pod discovery or developer-managed floor rendering * Lightweight floor metadata fetch before loading content  ---  ## Authorization & Context  * The API may be called by authenticated or unauthenticated users (depending on floor visibility). * The `is_owner` field is calculated **relative to the requesting user context** (if authenticated).  ---  ## Response Format  `application/json`  ---  ## Response Structure  ### Top-Level Fields  | Field        | Type                   | Description                                                      | | ------------ | ---------------------- | ---------------------------------------------------------------- | | `floor_id`   | String                 | Public, human-readable identifier of the floor                   | | `floor_uid`  | String                 | Internal unique identifier of the floor                          | | `title`      | String                 | Display title of the floor                                       | | `details`    | String                 | Short description or summary of the floor                        | | `floor_type` | String                 | Type of floor (`PUBLIC`, `PRIVATE`, `POD`)                       | | `is_owner`   | String (`\"0\"` / `\"1\"`) | Indicates whether the requesting user is the owner               | | `blocks`     | Array                  | List of blocks available in the floor                            | | `avatar`     | Object                 | Floor logo / avatar metadata                                     | | `app_id`     | String                 | Associated application ID (used mainly for pod/developer floors) |  ---  ## Ownership Indicator  ### `is_owner`  ```json \"is_owner\": \"0\" ```  | Value | Meaning                                   | | ----- | ----------------------------------------- | | `\"1\"` | Requesting user is the owner of the floor | | `\"0\"` | Requesting user is not the owner          |  This field is typically used by clients to:  * Enable or disable edit/settings UI * Show owner-only actions  ---  ## Blocks Object  ```json \"blocks\": [   {     \"BID\": \"1765960948723\",     \"type\": \"1\",     \"title\": \"Feeds\"   } ] ```  Each block represents a **content category or service** available inside the floor.  ### Block Fields  | Field   | Type   | Description                                           | | ------- | ------ | ----------------------------------------------------- | | `BID`   | String | Unique identifier of the block                        | | `type`  | String | Block type identifier (e.g., feed, blog, forum, quiz) | | `title` | String | Display name of the block                             |  ---  ## Avatar Object  ```json \"avatar\": {   \"id\": \"1767009204367\",   \"url\": \"https://...\" } ```  | Field | Type   | Description                    | | ----- | ------ | ------------------------------ | | `id`  | String | Media identifier of the avatar | | `url` | String | CDN URL of the floor logo      |  Used to render the floor’s profile image or banner.  ---  ## Floor Type  ```json \"floor_type\": \"POD\" ```  | Value     | Meaning                               | | --------- | ------------------------------------- | | `PUBLIC`  | Open floor visible to everyone        | | `PRIVATE` | Restricted floor                      | | `POD`     | Aggregated or developer-managed floor |  `POD` floors are often associated with an `app_id` and may aggregate or serve content programmatically.  ---  ## Sample Success Response  ```json {   \"is_owner\": \"0\",   \"blocks\": [     {       \"BID\": \"1765960948723\",       \"type\": \"1\",       \"title\": \"Feeds\"     }   ],   \"floor_uid\": \"1765960956967\",   \"floor_id\": \"raghupodfloor1\",   \"details\": \"raghu\",   \"avatar\": {     \"id\": \"1767009204367\",     \"url\": \"https://d2e5822u5ecuq8.cloudfront.net/room/1765960956967/logo/1765960956967.jpg\"   },   \"title\": \"raghu\",   \"floor_type\": \"POD\",   \"app_id\": \"1765949734005\" } ```  ---  ## Notes for Developers  * This is a **lightweight metadata API** and is safe to call frequently. * Use this API **before** loading posts or analytics. * `blocks` ordering can be used directly for navigation UI. * `floor_type` + `is_owner` together determine which UI actions are allowed.  ---  ## Common Error Scenarios  ### Floor Not Found  ```json {   \"status\": \"ERROR\",   \"message\": \"Floor not found\" } ```  ### Access Restricted  ```json {   \"status\": \"ERROR\",   \"message\": \"Access denied for this floor\" } ```  ---  ### Final Mental Model  > **This API answers: “What is this floor, who owns it, and what can I do here?”**
+     * Basic information of a floor
+     */
+    getFloorInformationRaw(requestParameters: GetFloorInformationRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<GetFloorInformation200Response>>;
+    /**
+     * This API returns the **basic profile information of a floor**. It is used to fetch all essential metadata required to **render a floor landing page, header, or navigation context**.  The response includes:  * Floor identity and type * Ownership information relative to the requesting user * Floor metadata (title, description, avatar) * List of blocks available in the floor * App association (for pod / developer use cases)  This API does **not** return posts or content; it only provides **structural and descriptive information** about the floor.  ---  ## Typical Use Cases  * Render floor header (title, logo, description) * Decide UI permissions (owner vs non-owner) * Display available blocks (Feeds, Blog, Quiz, etc.) * Pod discovery or developer-managed floor rendering * Lightweight floor metadata fetch before loading content  ---  ## Authorization & Context  * The API may be called by authenticated or unauthenticated users (depending on floor visibility). * The `is_owner` field is calculated **relative to the requesting user context** (if authenticated).  ---  ## Response Format  `application/json`  ---  ## Response Structure  ### Top-Level Fields  | Field        | Type                   | Description                                                      | | ------------ | ---------------------- | ---------------------------------------------------------------- | | `floor_id`   | String                 | Public, human-readable identifier of the floor                   | | `floor_uid`  | String                 | Internal unique identifier of the floor                          | | `title`      | String                 | Display title of the floor                                       | | `details`    | String                 | Short description or summary of the floor                        | | `floor_type` | String                 | Type of floor (`PUBLIC`, `PRIVATE`, `POD`)                       | | `is_owner`   | String (`\"0\"` / `\"1\"`) | Indicates whether the requesting user is the owner               | | `blocks`     | Array                  | List of blocks available in the floor                            | | `avatar`     | Object                 | Floor logo / avatar metadata                                     | | `app_id`     | String                 | Associated application ID (used mainly for pod/developer floors) |  ---  ## Ownership Indicator  ### `is_owner`  ```json \"is_owner\": \"0\" ```  | Value | Meaning                                   | | ----- | ----------------------------------------- | | `\"1\"` | Requesting user is the owner of the floor | | `\"0\"` | Requesting user is not the owner          |  This field is typically used by clients to:  * Enable or disable edit/settings UI * Show owner-only actions  ---  ## Blocks Object  ```json \"blocks\": [   {     \"BID\": \"1765960948723\",     \"type\": \"1\",     \"title\": \"Feeds\"   } ] ```  Each block represents a **content category or service** available inside the floor.  ### Block Fields  | Field   | Type   | Description                                           | | ------- | ------ | ----------------------------------------------------- | | `BID`   | String | Unique identifier of the block                        | | `type`  | String | Block type identifier (e.g., feed, blog, forum, quiz) | | `title` | String | Display name of the block                             |  ---  ## Avatar Object  ```json \"avatar\": {   \"id\": \"1767009204367\",   \"url\": \"https://...\" } ```  | Field | Type   | Description                    | | ----- | ------ | ------------------------------ | | `id`  | String | Media identifier of the avatar | | `url` | String | CDN URL of the floor logo      |  Used to render the floor’s profile image or banner.  ---  ## Floor Type  ```json \"floor_type\": \"POD\" ```  | Value     | Meaning                               | | --------- | ------------------------------------- | | `PUBLIC`  | Open floor visible to everyone        | | `PRIVATE` | Restricted floor                      | | `POD`     | Aggregated or developer-managed floor |  `POD` floors are often associated with an `app_id` and may aggregate or serve content programmatically.  ---  ## Sample Success Response  ```json {   \"is_owner\": \"0\",   \"blocks\": [     {       \"BID\": \"1765960948723\",       \"type\": \"1\",       \"title\": \"Feeds\"     }   ],   \"floor_uid\": \"1765960956967\",   \"floor_id\": \"raghupodfloor1\",   \"details\": \"raghu\",   \"avatar\": {     \"id\": \"1767009204367\",     \"url\": \"https://d2e5822u5ecuq8.cloudfront.net/room/1765960956967/logo/1765960956967.jpg\"   },   \"title\": \"raghu\",   \"floor_type\": \"POD\",   \"app_id\": \"1765949734005\" } ```  ---  ## Notes for Developers  * This is a **lightweight metadata API** and is safe to call frequently. * Use this API **before** loading posts or analytics. * `blocks` ordering can be used directly for navigation UI. * `floor_type` + `is_owner` together determine which UI actions are allowed.  ---  ## Common Error Scenarios  ### Floor Not Found  ```json {   \"status\": \"ERROR\",   \"message\": \"Floor not found\" } ```  ### Access Restricted  ```json {   \"status\": \"ERROR\",   \"message\": \"Access denied for this floor\" } ```  ---  ### Final Mental Model  > **This API answers: “What is this floor, who owns it, and what can I do here?”**
+     * Basic information of a floor
+     */
+    getFloorInformation(requestParameters: GetFloorInformationRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<GetFloorInformation200Response>;
+}