Skip to main content
Our SDK is pure TypeScript - no WASM or native dependencies. It works in browsers, React Native, and Node.js out of the box.

NPM Package

GitHub Repository

If the TypeScript SDK doesn’t work for your use case - whether you’re using a different language, need a custom integration, or have specific requirements - please reach out to us directly.

Contact us

Tell us about your project and we’ll work with you on a solution.

​
Iframe

Embed Satora Swaps directly into your application - no SDK integration required. Already used by Arkade Wallet, Alby Hub, and more.

​
Developer Portal

Sign up to track your swaps, manage referral codes, and monitor your integration.

Developer Portal

developer.satora.io

​
REST API

The REST API is not intended for direct production use. The API surface may change without notice and lacks guarantees around stability, rate limits, and support. We strongly recommend using the TypeScript SDK instead.

API Reference

Browse the full REST API documentation.

​
Client compatibility headers

SDK requests include a client identifier and one protocol epoch header per protocol component:
X-Lendaswap-Client identifies the SDK and SDK version. EVM-target swap creation requires a recognizable <sdk-name>/<semver> value. Each x-satora-<component>-version header carries the integer protocol epoch the client speaks for that component. Swap creation and the signing-sensitive per-swap endpoints check the components the swap uses and reject a client whose epoch for one of them is older than the server supports. Clients that still send the legacy x-satora-server-version header are accepted while every component is at epoch 1.