Rename floor

This API renames a floor by changing knowing the floor identifier (floor_id).

It allows the floor owner to update the public-facing floor ID (slug/handle) from an old value to a new value. This is typically used when the owner wants to rebrand, reorganize, or correct the floor’s identifier.

⚠️ This operation affects how the floor is accessed and referenced externally, so it must be performed carefully.

Ownership & Authorization (Critical)

The caller must be authenticated

Only the floor owner is allowed to rename a floor

Members, followers, or non-owners cannot perform this operation

Ownership is validated internally using user_id

If the user is not the owner, the request must be rejected.

Request Method

POST

Content-Type

application/x-www-form-urlencoded
(or equivalent form-data encoding)

Request Parameters (Form Fields)

Parameter	Type	Required	Description
`user_id`	String	Yes	User requesting the rename. Must be the owner of the floor.
`from`	String	Yes	Existing floor ID (current identifier to be renamed).
`to`	String	Yes	New floor ID to assign to the floor.
`app_id`	String	No	Identifier of the calling application (used mainly for pod/developer contexts).

Rename Rules & Constraints

The from floor ID must exist

The to floor ID must be unique and not already in use

The rename operation updates only the floor ID

Floor ownership, blocks, posts, and internal fid remain unchanged

Any links or references using the old floor ID may no longer be valid after rename

Behavior Summary

Scenario	Result
Valid owner + unique new ID	Floor ID renamed successfully
Non-owner user	Request rejected
`from` floor ID not found	Error
`to` floor ID already exists	Error
`from` == `to`	No-op or validation error (implementation choice)

Response Format

application/json

Sample Success Response

{
  "status": "SUCCESS",
  "old_floor_id": "oldfloorid",
  "new_floor_id": "newfloorid",
  "message": "Floor ID renamed successfully"
}

Sample Error Responses

Not Floor Owner

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

Floor Not Found

{
  "status": "ERROR",
  "message": "Source floor ID does not exist"
}

Floor ID Already Exists

{
  "status": "ERROR",
  "message": "Target floor ID is already in use"
}

Invalid Request

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

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

Authorization: Bearer ********************

Ownership & Authorization (Critical)#

Request Method#

Content-Type#

Request Parameters (Form Fields)#

Rename Rules & Constraints#

Behavior Summary#

Response Format#

Sample Success Response#

Sample Error Responses#

Not Floor Owner#

Floor Not Found#

Floor ID Already Exists#

Invalid Request#

Notes for Developers#

One-Line Mental Model#

Request

Responses