Authentication & Identity

FloorMemory APIs are identity-aware, but identity-agnostic.

This means:

Every request must identify a user

FloorMemory does not force how you authenticate that user

Authentication (Required)

All API calls require Bearer Token authentication.

Tokens:

Are generated per App

Authorize access to FloorMemory APIs

Must be kept server-side

Tokens are not user tokens.
They represent your application.

User Identity (Required)

Every conversational API requires a user_id.

user_id:

Identifies the end user

Must be stable and unique

Can come from your system or xFloor

Two Supported Identity Models

Option A — You Manage Users (Most Common)

Use this if:

You already have login (SSO, OAuth, email/password)

You want full control over users

How it works:

Authenticate users in your system

Pass your own user_id to FloorMemory APIs

Do NOT use Registration APIs

This is the recommended approach for most products.

Option B — xFloor Manages Users

Use this if:

You don’t have an auth system

You want OTP-based signup/login

How it works:

Use xFloor Registration APIs

Receive a persistent xfloor_user_id

Use that ID in all APIs

Rule of Thumb

User identity is mandatory.
Registration APIs are optional.

If you already have users → skip registration entirely.

Authentication and Identification

Authentication & Identity#

Authentication (Required)#

User Identity (Required)#

Two Supported Identity Models#

Option A — You Manage Users (Most Common)#

Option B — xFloor Manages Users#