Skip to main content
KeyStone provides two types of client libraries, each designed for a different part of your stack:

Backend SDKs vs Frontend Packages


Backend SDKs

For server-side integration. Use M2M credentials to access the full API.

TypeScript / Node.js

@keystoneos/sdk - Node.js 20+, zero dependencies. Handles auth, retries, idempotency, and webhook verification.

Python

keystoneos - Python 3.10+, async and sync clients. Full Pydantic models for all types.

What the SDKs handle


Frontend Integration

Embed settlement UI into your platform’s web app. The frontend packages use session tokens (created by your backend) for scoped API access.

React Hooks

@keystoneos/react - Headless hooks for settlements, instructions, deposits. Bring your own UI.

Server Setup

@keystoneos/node - The backend side of the frontend integration: session tokens and webhook verification.

Components

KeystoneProvider - Wrap your app to enable all hooks.

What the frontend integration covers


When to use what

Every endpoint in the API Reference works with any HTTP client. The SDKs and packages are convenience layers, not a separate API.

Quick comparison