@xfloor/floor-memory-sdk-ts 1.0.20 → 1.0.22

package/dist/apis/EventApi.js

@@ -168,6 +168,75 @@ var EventApi = /** @class */ (function (_super) {
             });
         });
     };
+    /**
+     * This API retrieves the **latest posts (events)** from a specified floor.  The behaviour of the API changes based on whether a **user ID** is provided:  * **If `user_id` is provided**   → The API returns **recent posts relevant to that user**, scoped within the given floor.   This includes posts from:    * Floors the user follows   * Floors created by the user   * Pod floors associated with the user (if applicable)  * **If `user_id` is NOT provided**   → The API returns the **most recent posts available in the specified floor**, without user-specific filtering.  This makes the API suitable for:  * Personalized activity feeds * Floor-level public timelines * Pod-based content aggregation * Developer-built pods and custom clients  ---  ## **Key Concepts**  * A **floor** represents a content space (independent floor, followed floor, or pod floor) * A **pod floor** may aggregate content across multiple related floors * Posts are returned **in reverse chronological order** (latest first) * Each post belongs to a specific **block** within the floor  ---  ## **Request Method**  `GET`  ---  ## **Request Parameters (Query Params)**  | Parameter Name | Type   | Required | Description                                                                                                                | | -------------- | ------ | -------- | -------------------------------------------------------------------------------------------------------------------------- | | `floor_id`     | String | **Yes**  | Floor identifier from which events should be fetched. Can be a pod floor ID, followed floor ID, or an independent floor ID | | `user_id`      | String | No       | If provided, returns posts relevant to the user within the given floor                                                     | | `app_id`       | String | No       | Identifier for external developers or pod-based applications consuming this API                                            |  ---  ## **Behavior Summary**  | Scenario               | Result                                    | | ---------------------- | ----------------------------------------- | | `floor_id` only        | Latest posts from the specified floor     | | `floor_id` + `user_id` | User-relevant posts within that floor     | | Pod floor ID           | Aggregated posts across pod-linked floors | | Independent floor ID   | Posts only from that floor                |  ---  ## **Response Format**  `application/json`  ---  ## **Response Structure**  ### **Top-Level Fields**  | Field        | Type   | Description                    | | ------------ | ------ | ------------------------------ | | `post_count` | String | Total number of posts returned | | `items`      | Array  | List of recent post objects    |  ---  ### **Post Object (`items[]`)**  | Field           | Type   | Description                                                               | | --------------- | ------ | ------------------------------------------------------------------------- | | `event_id`      | String | Unique identifier of the post/event                                       | | `block_type`    | String | Type of block where the post was created (e.g., blog, forum, audio, etc.) | | `block_id`      | String | Identifier of the block within the floor                                  | | `floor_uid`     | String | Floor identifier where the post belongs                                   | | `title`         | String | Title of the post (may be empty)                                          | | `text`          | String | Text or HTML content of the post                                          | | `media`         | Array  | Media objects (audio, image, etc.), if any                                | | `created_at_ms` | String | Post creation time in milliseconds (epoch)                                |  ---  ### **Author Object**  | Field       | Type   | Description                  | | ----------- | ------ | ---------------------------- | | `name`      | String | Display name of the author   | | `floor_uid` | String | Author’s floor/user handle   | | `avatar`    | Object | Author profile image details |  ---  ### **Media Object**  | Field  | Type   | Description                         | | ------ | ------ | ----------------------------------- | | `type` | String | Media type (e.g., `AUDIO`, `IMAGE`) | | `url`  | String | Public URL of the media file        |  ---  ## **Sample Success Response**  *(structure abbreviated for clarity)*  ```json {   \"post_count\": \"18\",   \"items\": [     {       \"event_id\": \"1766557274836\",       \"block_type\": \"0\",       \"title\": \"voice-note-1766557272764.wav\",       \"text\": \"You\",       \"created_at_ms\": \"1766557275000\",       \"author\": {         \"name\": \"MEGHANA G\",         \"floor_uid\": \"meghanag\",         \"avatar\": {           \"type\": \"IMAGE\",           \"url\": \"https://...\"         }       },       \"media\": [         {           \"type\": \"AUDIO\",           \"url\": \"https://...\"         }       ]     }   ] } ```  ---  ## **Notes**  * Posts may contain **plain text or HTML** * Media is optional and may be absent * Ordering is **latest first** * The API is read-only and does not require authentication by default * Access control (public/private floors) is enforced internally  ---  ## **Typical Use Cases**  * Floor activity feed * Pod-level dashboards * User-personalized timelines * Public floor landing pages * External developer pods using `app_id`
+     * Recent Events
+     */
+    EventApi.prototype.getRecentEventsRaw = function (requestParameters, initOverrides) {
+        return __awaiter(this, void 0, void 0, function () {
+            var queryParameters, headerParameters, token, tokenString, 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 getRecentEvents().');
+                        }
+                        if (requestParameters['appId'] == null) {
+                            throw new runtime.RequiredError('appId', 'Required parameter "appId" was null or undefined when calling getRecentEvents().');
+                        }
+                        queryParameters = {};
+                        if (requestParameters['userId'] != null) {
+                            queryParameters['user_id'] = requestParameters['userId'];
+                        }
+                        if (requestParameters['floorId'] != null) {
+                            queryParameters['floor_id'] = requestParameters['floorId'];
+                        }
+                        if (requestParameters['appId'] != null) {
+                            queryParameters['app_id'] = requestParameters['appId'];
+                        }
+                        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:
+                        urlPath = "/api/memory/recent/events";
+                        return [4 /*yield*/, this.request({
+                                path: urlPath,
+                                method: 'GET',
+                                headers: headerParameters,
+                                query: queryParameters,
+                            }, initOverrides)];
+                    case 3:
+                        response = _a.sent();
+                        return [2 /*return*/, new runtime.JSONApiResponse(response, function (jsonValue) { return (0, index_1.GetRecentEvents200ResponseFromJSON)(jsonValue); })];
+                }
+            });
+        });
+    };
+    /**
+     * This API retrieves the **latest posts (events)** from a specified floor.  The behaviour of the API changes based on whether a **user ID** is provided:  * **If `user_id` is provided**   → The API returns **recent posts relevant to that user**, scoped within the given floor.   This includes posts from:    * Floors the user follows   * Floors created by the user   * Pod floors associated with the user (if applicable)  * **If `user_id` is NOT provided**   → The API returns the **most recent posts available in the specified floor**, without user-specific filtering.  This makes the API suitable for:  * Personalized activity feeds * Floor-level public timelines * Pod-based content aggregation * Developer-built pods and custom clients  ---  ## **Key Concepts**  * A **floor** represents a content space (independent floor, followed floor, or pod floor) * A **pod floor** may aggregate content across multiple related floors * Posts are returned **in reverse chronological order** (latest first) * Each post belongs to a specific **block** within the floor  ---  ## **Request Method**  `GET`  ---  ## **Request Parameters (Query Params)**  | Parameter Name | Type   | Required | Description                                                                                                                | | -------------- | ------ | -------- | -------------------------------------------------------------------------------------------------------------------------- | | `floor_id`     | String | **Yes**  | Floor identifier from which events should be fetched. Can be a pod floor ID, followed floor ID, or an independent floor ID | | `user_id`      | String | No       | If provided, returns posts relevant to the user within the given floor                                                     | | `app_id`       | String | No       | Identifier for external developers or pod-based applications consuming this API                                            |  ---  ## **Behavior Summary**  | Scenario               | Result                                    | | ---------------------- | ----------------------------------------- | | `floor_id` only        | Latest posts from the specified floor     | | `floor_id` + `user_id` | User-relevant posts within that floor     | | Pod floor ID           | Aggregated posts across pod-linked floors | | Independent floor ID   | Posts only from that floor                |  ---  ## **Response Format**  `application/json`  ---  ## **Response Structure**  ### **Top-Level Fields**  | Field        | Type   | Description                    | | ------------ | ------ | ------------------------------ | | `post_count` | String | Total number of posts returned | | `items`      | Array  | List of recent post objects    |  ---  ### **Post Object (`items[]`)**  | Field           | Type   | Description                                                               | | --------------- | ------ | ------------------------------------------------------------------------- | | `event_id`      | String | Unique identifier of the post/event                                       | | `block_type`    | String | Type of block where the post was created (e.g., blog, forum, audio, etc.) | | `block_id`      | String | Identifier of the block within the floor                                  | | `floor_uid`     | String | Floor identifier where the post belongs                                   | | `title`         | String | Title of the post (may be empty)                                          | | `text`          | String | Text or HTML content of the post                                          | | `media`         | Array  | Media objects (audio, image, etc.), if any                                | | `created_at_ms` | String | Post creation time in milliseconds (epoch)                                |  ---  ### **Author Object**  | Field       | Type   | Description                  | | ----------- | ------ | ---------------------------- | | `name`      | String | Display name of the author   | | `floor_uid` | String | Author’s floor/user handle   | | `avatar`    | Object | Author profile image details |  ---  ### **Media Object**  | Field  | Type   | Description                         | | ------ | ------ | ----------------------------------- | | `type` | String | Media type (e.g., `AUDIO`, `IMAGE`) | | `url`  | String | Public URL of the media file        |  ---  ## **Sample Success Response**  *(structure abbreviated for clarity)*  ```json {   \"post_count\": \"18\",   \"items\": [     {       \"event_id\": \"1766557274836\",       \"block_type\": \"0\",       \"title\": \"voice-note-1766557272764.wav\",       \"text\": \"You\",       \"created_at_ms\": \"1766557275000\",       \"author\": {         \"name\": \"MEGHANA G\",         \"floor_uid\": \"meghanag\",         \"avatar\": {           \"type\": \"IMAGE\",           \"url\": \"https://...\"         }       },       \"media\": [         {           \"type\": \"AUDIO\",           \"url\": \"https://...\"         }       ]     }   ] } ```  ---  ## **Notes**  * Posts may contain **plain text or HTML** * Media is optional and may be absent * Ordering is **latest first** * The API is read-only and does not require authentication by default * Access control (public/private floors) is enforced internally  ---  ## **Typical Use Cases**  * Floor activity feed * Pod-level dashboards * User-personalized timelines * Public floor landing pages * External developer pods using `app_id`
+     * Recent Events
+     */
+    EventApi.prototype.getRecentEvents = 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.getRecentEventsRaw(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/FloorApi.d.ts

@@ -0,0 +1,99 @@
+/**
+ * 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 { EditFloor200Response, FloorInfo } from '../models/index';
+export interface EditFloorRequest {
+    floorId: string;
+    userId: string;
+    appId: string;
+    logoFile?: Blob;
+    title?: string;
+    details?: string;
+}
+export interface GetFloorInformationRequest {
+    floorId: string;
+    appId: string;
+    userId?: string;
+}
+export interface MakeFloorPrivateRequest {
+    floorId: string;
+    userId: string;
+    appId: string;
+}
+export interface MakeFloorPublicRequest {
+    floorId: string;
+    userId: string;
+    appId: string;
+}
+export interface RenameFloorRequest {
+    userId: string;
+    appId: string;
+    from: string;
+    to: string;
+}
+/**
+ *
+ */
+export declare class FloorApi 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                              | | ---------- | ------ | ------------ | ---------------------------------------- | | `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<EditFloor200Response>>;
+    /**
+     * 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                              | | ---------- | ------ | ------------ | ---------------------------------------- | | `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<EditFloor200Response>;
+    /**
+     * 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\": [   {     \"block_id\": \"1765960948723\",     \"type\": \"1\",     \"title\": \"Feeds\"   } ] ```  Each block represents a **content category or service** available inside the floor.  ### Block Fields  | Field   | Type   | Description                                           | | ------- | ------ | ----------------------------------------------------- | | `block_id`   | 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\": [     {       \"block_id\": \"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<FloorInfo>>;
+    /**
+     * 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\": [   {     \"block_id\": \"1765960948723\",     \"type\": \"1\",     \"title\": \"Feeds\"   } ] ```  Each block represents a **content category or service** available inside the floor.  ### Block Fields  | Field   | Type   | Description                                           | | ------- | ------ | ----------------------------------------------------- | | `block_id`   | 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\": [     {       \"block_id\": \"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<FloorInfo>;
+    /**
+     * 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).
+     * Make floor Private
+     */
+    makeFloorPrivateRaw(requestParameters: MakeFloorPrivateRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<EditFloor200Response>>;
+    /**
+     * 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).
+     * Make floor Private
+     */
+    makeFloorPrivate(requestParameters: MakeFloorPrivateRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<EditFloor200Response>;
+    /**
+     * 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.”**
+     * Make floor public
+     */
+    makeFloorPublicRaw(requestParameters: MakeFloorPublicRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<EditFloor200Response>>;
+    /**
+     * 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.”**
+     * Make floor public
+     */
+    makeFloorPublic(requestParameters: MakeFloorPublicRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<EditFloor200Response>;
+    /**
+     * 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.”**
+     * Rename floor
+     */
+    renameFloorRaw(requestParameters: RenameFloorRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<EditFloor200Response>>;
+    /**
+     * 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.”**
+     * Rename floor
+     */
+    renameFloor(requestParameters: RenameFloorRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<EditFloor200Response>;
+}