Keyban APIs & SDKs
Keyban offers a modular set of SDKs and APIs that let you build rich, secure, and scalable Web3 applications. Whether you're integrating in a React frontend, a Node.js backend, or communicating directly via REST, our developer tools support your workflows end-to-end.
Overview
Our SDKs are designed to be used alongside the Embedded Wallet SDK, or independently if you bring your own wallet solution. REST APIs are reserved for Digital Product Passport (DPP) use cases and do not overlap with SDK functionality.
Each option offers a different integration path:
| Tool | Environment | Typical Usage |
|---|---|---|
| WAAS React SDK | Web (React) | Drop-in components and hooks to manage wallet sessions and blockchain interactions. |
| JavaScript SDK | Node.js / Browser | Programmatic access to tokens, NFTs, identities, and smart contracts. |
| REST API | Any HTTP client | API access to manage Digital Product Passport (DPP) data and workflows. |
WAAS React SDK
A high-level SDK tailored for React apps. It integrates the Wallet-as-a-Service functionality with minimal boilerplate.
- 🔗 Documentation
- 📦 Provides React hooks and context
- 🎯 Handles session lifecycle and secure signing
JavaScript SDK
A lower-level SDK that abstracts Keyban protocol interactions in Node.js or browser environments.
- 🔗 Documentation
- 🔑 Interact with on-chain assets, metadata, and user profiles
- ⚙️ Can be used in combination with any wallet implementation
REST API
A dedicated HTTP API layer for managing Digital Product Passport use cases. This interface provides backend access to structured product data, transfer history, and compliance metadata.
- 🔗 API Reference
- 📡 Ideal for server-side processing, mobile apps, and headless use cases
- 🔐 Supports authenticated calls using session tokens or delegated identities
When to Use Which?
Note: The REST API is not a general-purpose backend interface. It is scoped specifically to the Digital Product Passport domain.
Choose the tool based on your project architecture and developer stack:
- If you're building a React SPA: use the WAAS React SDK for the smoothest integration.
- If you're working on custom logic in Node.js: use the JS SDK for flexibility.