FloorMemory SDKs

FloorMemory SDKs provide a typed, language-native interface to the FloorMemory APIs.

They are designed to:

Simplify authentication handling

Enforce request/response schemas

Reduce boilerplate HTTP code

Remain thin wrappers over the APIs

SDKs do not introduce custom behavior and do not hide API semantics.
They map closely to the underlying REST endpoints.

Supported SDKs

FloorMemory provides official SDKs for:

Python

JavaScript

TypeScript

Java

All SDKs are generated from the same OpenAPI specification and are functionally equivalent.

This ensures:

Contract consistency across languages

Identical request/response behavior

Uniform parameter semantics

Predictable version alignment

Source Code

All SDK source code is open source and maintained on GitHub:

👉 https://github.com/xFloorllm/floor-memory-sdk-client

The repository contains:

Python SDK

JavaScript SDK

TypeScript SDK

Java SDK

SDK releases track API contract versions and are versioned in alignment with the FloorMemory API.

Official Examples (All Languages)

Production-ready integration examples are available here:

👉 https://github.com/xFloorllm/floor-memory-sdk-examples

This repository includes examples for:

Python

JavaScript

TypeScript

Java

The examples demonstrate:

Proper authentication configuration

Correct app_id handling

Multi-turn conversational flows

Event ingestion patterns

Production-safe initialization

Clean service-layer integration

If you are building a real application, the examples repository should be your starting point.

When to Use an SDK vs REST

Use an SDK if you want:

Faster integration

Typed request/response models

Automatic serialization/deserialization

Consistent error handling

Reduced HTTP boilerplate

Use REST directly if:

You need full HTTP-level control

Your environment does not support SDKs

You are building infrastructure-level tooling

Both approaches are fully supported and share the same API contract.

Versioning Policy

SDK versions align with the FloorMemory API contract.

Patch releases → Documentation, tooling, or non-functional fixes

Minor releases → Backward-compatible API additions

Major releases → Breaking API changes

SDK updates are contract-driven. There is no SDK-specific behavior divergence.

Design Philosophy

FloorMemory SDKs are intentionally:

Thin

Predictable

Contract-aligned

Explicit in parameter handling

There are no hidden abstractions, no implicit defaults, and no behavioral overrides beyond what the API specifies.

Overview

FloorMemory SDKs#

Supported SDKs#

Source Code#

Official Examples (All Languages)#

When to Use an SDK vs REST#

Use an SDK if you want:#

Use REST directly if:#

Versioning Policy#

Design Philosophy#