@xfloor-memory-sdk
  1. Core FloorMemory
@xfloor-memory-sdk
  • Get Started
    • Overview
    • Quick Start
    • Authentication and Identification
    • Core Concepts (5-Minute Read)
    • What to Use First (API Map)
  • SDK
    • Overview
    • SDK Installation & Setup
    • Python SDK
    • JavaScript SDK
    • Typescript SDK
    • Java SDK
    • FAQ & Troubleshooting
    • Copy-Paste Debug Checklists
  • Core FloorMemory
    • Query (Primary API)
      POST
    • Create Event (Post Content)
      POST
    • Recent Events
      GET
    • Basic information of a floor
      GET
  • Floor Management
    • Edit floor
      POST
    • Make floor Private
      POST
    • Make floor public
      POST
    • Rename floor
      POST
  • Registration
    • Sign Up
      POST
    • Sign In with email ID
      POST
    • Sign In with Mobile number
      POST
    • Validation
      POST
    • Change Password
      POST
    • Reset Password
      POST
    • Change email ID
      POST
    • Change Mobile number
      POST
    • Send Validation code
      POST
    • External User Registration
      POST
  • SDKs
  • Schemas
    • PostAdd
    • QueryResponse
    • Media
    • UserDetails
    • SignUpResponse
    • BlockDetails
    • FloorInfo
    • Threads
    • EventResponse
    • 400ErrorCode
    • Remaining
  1. Core FloorMemory

Basic information of a floor

GET
/api/memory/floor/info/{floor_id}
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#

FieldTypeDescription
floor_idStringPublic, human-readable identifier of the floor
floor_uidStringInternal unique identifier of the floor
titleStringDisplay title of the floor
detailsStringShort description or summary of the floor
floor_typeStringType of floor (PUBLIC, PRIVATE, POD)
is_ownerString ("0" / "1")Indicates whether the requesting user is the owner
blocksArrayList of blocks available in the floor
avatarObjectFloor logo / avatar metadata
app_idStringAssociated application ID (used mainly for pod/developer floors)

Ownership Indicator#

is_owner#

"is_owner": "0"
ValueMeaning
"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#

"blocks": [
  {
    "block_id": "1765960948723",
    "type": "1",
    "title": "Feeds"
  }
]
Each block represents a content category or service available inside the floor.

Block Fields#

FieldTypeDescription
block_idStringUnique identifier of the block
typeStringBlock type identifier (e.g., feed, blog, forum, quiz)
titleStringDisplay name of the block

Avatar Object#

"avatar": {
  "id": "1767009204367",
  "url": "https://..."
}
FieldTypeDescription
idStringMedia identifier of the avatar
urlStringCDN URL of the floor logo
Used to render the floor’s profile image or banner.

Floor Type#

"floor_type": "POD"
ValueMeaning
PUBLICOpen floor visible to everyone
PRIVATERestricted floor
PODAggregated or developer-managed floor
POD floors are often associated with an app_id and may aggregate or serve content programmatically.

Sample Success Response#

{
  "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#

{
  "status": "ERROR",
  "message": "Floor not found"
}

Access Restricted#

{
  "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?”

Request

Authorization
Provide your bearer token in the
Authorization
header when making requests to protected resources.
Example:
Authorization: Bearer ********************
Path Params

Query Params

Responses

🟢200Success
application/json
Body

🟠400BadRequest
Request Request Example
Shell
JavaScript
Java
Swift
curl --location --request GET 'https://appfloor.in/api/memory/floor/info/?user_id=1345896753484&app_id=1387654378393' \
--header 'Authorization: Bearer <token>'
Response Response Example
200 - Example 1
{
    "floor_id": "string",
    "title": "string",
    "details": "string",
    "floor_uid": "string",
    "blocks": [
        {
            "block_id": "string",
            "type": "string",
            "title": "string"
        }
    ],
    "avatar": {
        "url": "string",
        "type": "string"
    },
    "is_owner": "string",
    "floor_type": "string",
    "app_id": "string"
}
Modified at 2026-01-28 05:20:38
Previous
Recent Events
Next
Edit floor
Built with