@xfloor-memory-sdk
    @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

    Registration

    When Should These APIs Be Used?#

    These registration APIs should be used only if the application relies on xFloor for user registration, authentication, and account management.
    Applications that:
    Already have an existing user base, or
    Prefer to manage users using their own authentication system (e.g., OAuth, SSO, enterprise IAM, custom login)
    are not required to call these APIs.
    In such cases:
    The developer manages user creation, login, password handling, and recovery.
    The application simply passes a valid user identifier to xFloor when invoking other APIs.
    xFloor treats the user as an externally authenticated user.
    Regardless of the registration method:
    All subsequent API calls must include a valid user context.
    The responsibility for user authenticity lies with the system that performs authentication.
    xFloor reserves the right to enforce rate limits, abuse prevention, and usage policies at the API level.
    Modified at 2025-12-19 14:02:14
    Previous
    Rename floor
    Next
    Sign Up
    Built with