Welcome — Build with Trezor Suite®
This Developer Portal helps you get started quickly with the Trezor Suite® platform. Read the Getting Started guide, run SDK examples, explore the API reference, and deploy secure integrations.
Why choose Trezor Suite® for your wallet integration?
Trezor Suite® provides a deterministic hardware-wallet-backed signing flow which keeps private keys on-device while exposing clean API primitives. Use the Trezor Suite® SDK and Trezor Suite APIs to perform device pairing, account discovery, transaction creation, and secure signing — all while following recommended security patterns. This portal contains tutorials, sandbox examples, and production hardening guidelines.
Getting started in 5 minutes
- Install the Trezor Suite® SDK (JavaScript/TypeScript sample included below).
- Create a developer account and generate sandbox API keys.
- Run the simulator or connect your Trezor device via USB/WebUSB.
- Try the example: discover accounts, build a transaction, and sign it securely.
- Review security best practices and deploy to production.
// Example: connect and request device features (JS)
import Trezor from 'trezor-suite-sdk';
async function demo(){
const sdk = new Trezor({apiKey: 'SANDBOX_KEY'});
const device = await sdk.connect(); // pair with device
const features = await device.getFeatures(); // device info & capabilities
console.log('Connected to', features.model);
}
Core resources
Security-first workflow
Trezor Suite® emphasizes that private keys never leave the hardware device. Our recommended integration pattern uses device-backed signing: compose transactions on your backend, request a signature via the SDK, and receive a signed payload without exposing private keys. Follow the Security Checklist in this portal to harden transports, validate firmware versions, and use attestation where available.
Learn by doing — Sandbox & Simulator
Use the sandbox environment to test account discovery, transaction building, and signing flows. The simulator mimics device responses for CI jobs and automated tests. Stubbing the SDK in tests speeds development while keeping a path to full device integration.
# Run tests using the simulator npm run test -- --env=simulator