@xfloor-memory-sdk
  1. Registration
@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
    • Make floor Private
    • Make floor public
    • Rename floor
  • 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. Registration

Sign Up

POST
/auth-service/sign/up
Creates a new user account in the Floor POD using either a mobile number or an email ID.
At least one of mobile_number or email_id is required to register a user. Both may be provided if available.
The API registers the user under the specified application context and prepares the account for subsequent authentication and usage.
Upon successful registration, the API returns:
a unique user_id identifying the newly created user, and
a success string indicating the outcome of the sign-up operation.
The user account is created under the specified application context and can be used for subsequent interactions with Floor POD APIs.

Parameter Clarification (Recommended)#

name is mandatory for user profile creation
Either mobile_number or email_id must be present
app_id is optional and used to associate the user with a specific application

Request

Authorization
Provide your bearer token in the
Authorization
header when making requests to protected resources.
Example:
Authorization: Bearer ********************
Body Params multipart/form-dataRequired

Responses

🟢200Success
application/json
Body

🟠400BadRequest
Request Request Example
Shell
JavaScript
Java
Swift
curl --location --request POST 'https://appfloor.in/auth-service/sign/up' \
--header 'Authorization: Bearer <token>' \
--form 'name="Jon Doe"' \
--form 'email_id="myemail@email.com"' \
--form 'mobile_number="9084568934"' \
--form 'password="xxxxxxxx"' \
--form 'app_id="1675645678908"'
Response Response Example
200 - Example 1
{
    "user_id": "string",
    "success": "string",
    "name": "string"
}
Modified at 2026-02-16 04:33:59
Previous
Registration
Next
Sign In with email ID
Built with