@xfloor-memory-sdk
  1. Floor Management
@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. Floor Management

Make floor public

POST
/api/memory/make/floor/public/{floor_id}
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)#

FieldTypeRequiredDescription
user_idStringYesUser requesting the change. Must be the owner of the floor.
floor_idStringYesPublic identifier of the floor whose visibility is to be changed.
app_idStringNoIdentifier 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#

{
  "status": "SUCCESS",
  "floor_id": "my_floor",
  "visibility": "PUBLIC",
  "message": "Floor is now public"
}

Sample No-Op Response (Already Public)#

{
  "status": "SUCCESS",
  "floor_id": "my_floor",
  "visibility": "PUBLIC",
  "message": "Floor is already public"
}

Error Responses (Examples)#

Not Authorized (Not Owner)#

{
  "status": "ERROR",
  "message": "Only the floor owner can change floor visibility"
}

Floor Not Found#

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

Invalid Request#

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

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

🟠400InvalidFloorID
Request Request Example
Shell
JavaScript
Java
Swift
curl --location --request POST 'https://appfloor.in/api/memory/make/floor/public/?user_id&app_id' \
--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-02-13 08:35:02
Previous
Make floor Private
Next
Rename floor
Built with