Introduction
Welcome to the Trezor Suite Developer Portal — a place where developers can learn how to safely integrate hardware-backed keys, create wallet experiences, or build developer tools that interoperate with the Trezor Suite desktop and web applications. This guide is written for software engineers, product managers, and security-conscious teams who want a concise but practical on-ramp. It covers everything from installation to production hardening and includes code snippets and design tips.
Who is this for?
If you build wallets, custody solutions, DeFi integrations, or signing tools, this guide is for you. You'll learn how the Suite communicates with devices, what SDKs and APIs to use, and how to keep users safe while delivering excellent UX.
What you'll get
A clear path to get started, working examples, and a checklist you can use when shipping integrations with Trezor hardware wallets.
Quick callouts
- Device-first security model — private keys never leave the device.
- Multiple integration paths — web connectors, native apps, and CLI tooling.
- Comprehensive developer docs and SDKs for common languages.
Install & Setup
Before you can build, ensure you have the Trezor Suite app (desktop or web) for testing and a physical Trezor device. Use a dedicated development device when possible. This section walks through installing the Suite, connecting a device, and configuring your environment.
Environment checklist
Make sure you have:
- Node.js (LTS) and npm/yarn
- A modern browser (Chrome, Firefox, Edge)
- A Trezor Model T or Model One (for device testing)
- USB cable and, optionally, a USB hub for multiple devices
Connecting your Trezor
Trust prompts from the Suite and always verify the device model and fingerprint. When your device is connected, you'll use the Suite's built-in developer options or the trezor-connect library to interact programmatically.
Install example: add trezor-connect
npm install trezor-connect
# or
yarn add trezor-connectUsage (basic):
import TrezorConnect from 'trezor-connect';
TrezorConnect.init({
manifest: { email: 'dev@example.com', appUrl: 'https://your-app.example' }
});
const res = await TrezorConnect.getAccountInfo({ coin: 'btc' });
console.log(res);APIs & SDKs
Trezor provides multiple integration layers. Choose the right one for your product:
Trezor Connect
A browser-friendly bridge that exposes a secure API for signing, getting public keys, and managing accounts. It uses an explicit manifest to identify your app and runs with strong user consent flows.
Transport & Bridge
Transport libraries (USB/HID/WebUSB) power the connection between Suite and devices. Trezor's bridge sometimes helps when WebUSB is not available; always fall back gracefully if a connection method is blocked.
Language SDKs
There are SDKs and community-built libraries for TypeScript/JavaScript, Python, Go, and Rust. These are useful for backend signing tools or CLIs where the device can be connected to a server (rare) or a dedicated signing host.
Best practice: keep UX explicit
Never automate confirmation flows that should be user-approved on the device. Prompt clear messages and show the full transaction metadata in your UI before calling the device to sign.
Security Considerations
Security is the primary motivation for using hardware wallets. This section summarises recommended practices when building with Trezor devices.
Secrets never leave device
Private keys are held in secure storage on the device. Signing operations return only signatures and public data. Design your server infrastructure so you don't accidentally store ephemeral signing payloads or private keys.
Manifest & origin verification
Register a clear manifest for web integrations — it helps users verify the app origin when the device prompts for confirmation.
Transport security
Prefer WebUSB or native bridge with updated TLS for any server connections. Avoid exposing RPC endpoints that accept raw signing requests without authentication.
Storing backups
Encourage users to securely store recovery seeds. Never ask users to share these seeds with your app. If your product involves custodial flows, separate custody responsibilities and document them clearly for compliance.
Examples & Code Patterns
Here are practical code examples and UI patterns you'll find helpful while integrating Trezor Suite.
Example: Requesting a public key
const pk = await TrezorConnect.getPublicKey({
path: "m/44'/0'/0'/0/0",
coin: 'btc'
});
if (pk.success) console.log('xpub', pk.payload.xpub);
Example: Signing a transaction
Prepare the transaction data server-side and present a full summary in your UI. Then call the signing method:
const sign = await TrezorConnect.signTransaction({
inputs: [...],
outputs: [...],
coin: 'btc'
});
if (sign.success) submitToNetwork(sign.payload);
UI pattern: explicit review screen
Before any signing call, show a review step that highlights the amount, destination, fees, and network. Use high-contrast, accessible text and a large confirm button that states the exact action (eg. "Confirm send 0.25 BTC").
Logging & telemetry
Log only non-sensitive telemetry (errors, user flows, time-to-confirm). Never log seeds, private keys, or full raw transactions containing private inputs. Ensure compliance with privacy regulations like GDPR.
Troubleshooting & FAQ
Common problems and how to resolve them when developing with Trezor Suite.
Device not detected
Check USB cables, try a different port, enable WebUSB in your browser, or install the Trezor Bridge. Ensure USB permissions are granted to the browser.
Signing fails
Verify transaction format, coin support, and that the device firmware is up-to-date. Use developer logs from trezor-connect to capture the error payloads.
Sandboxing your tests
Use testnets and a separate test device. Never use real funds while experimenting with unvetted code paths.
Support channels
Refer to the official developer docs, community forums, and GitHub repositories for up-to-date issues and workarounds.
Conclusion
Building with Trezor Suite brings strong device-backed security to your applications. Follow best practices: keep the UX explicit, limit data retention, and always surface device confirmations to the user. With the examples and checklist in this guide you should be well-equipped to ship integrations that are both secure and user-friendly.
Next steps
Try the quick-start examples above, register your app manifest, and test with a dedicated device on a testnet. Revisit the security checklist before moving to production.