Ledger Live Integrations - Ledger Developer Portal

Executive summary

Ledger Live integration provides three primary paths: (1) Accounts / Blockchain integration to add native chain support, (2) Live Apps (Discover) to embed web3 dApps inside Ledger Live with secure signing flows, and (3) Device Apps that run on Ledger hardware for protocol-level signing. Each path has distinct requirements, deliverables and review processes; selecting the right path early simplifies design, security review and submission.

Integration paths (high-level)

Accounts / Blockchain integration

This path adds your blockchain so users can create and manage native accounts inside Ledger Live. It is appropriate when you want Ledger Live to display balances, transaction history and perform native sends/receives. Expect to provide an implementation, documentation, test vectors and sign agreements with Ledger prior to public release.

Live Apps (Discover)

Live Apps are web-based dApps embedded in Ledger Live’s Discover section. They use the Ledger Services Kit and Wallet API to request clear signing flows from the user, enabling secure contract interactions without blind signing. This is the recommended route for most dApps and DeFi integrations that need an in-app UX while leveraging user hardware for signing.

Device Apps

Device Apps run directly on Ledger hardware (applications written in C, Rust or other supported languages). Use this path when you require on-device key derivation or protocol-level operations that must not leave the device. Device Apps undergo a rigorous submission and testing process.

Developer workflow (recommended)

1 — Choose your integration path

Map your product goals to the path above. If you want account visibility and management, choose Accounts. If you expect complex dApp interactions with contract signatures, choose Live Apps. If signature logic must be on-device, select Device Apps.

2 — Read the docs & templates

Follow the official guides, example repos and the submission deliverables checklist. Templates include documentation, tests, endpoints (for Buy/Sell integrations), and sample UI patterns to match Ledger Live’s UX expectations.

3 — Build, test & iterate

Use the Ledger Services Kit Client and Wallet API for Live Apps, run Ledger Live locally for testing, and add integration tests and clear signing flows. For marketplace-style integrations (Buy / Sell / Exchange providers) implement the required backend endpoints and capability responses.

4 — Submit & collaborate

Most integrations require a submission form or an invitation. Engage Ledger early (there are forms and contact addresses in the Discover and Accounts docs) — this reduces rework and accelerates review.

Security & UX considerations

Clear signing

Design requests so the user sees explicit, human-readable signing information. Ledger Live’s tooling aims to prevent blind signing; ensure your smart contract calls include descriptive messages or structured data the wallet can render.

Least privilege

Request only the scopes and permissions you need. For third-party providers (Buy / Sell) follow Ledger's backend contract for the minimum required endpoints and scope responses.

Robust error handling

Gracefully handle declines, device disconnections, and network timeouts; show actionable UI states to the user so they understand both success and failure conditions.

Operational & integration checklist

Read corresponding Ledger docs for your path (Accounts / Discover / Device Apps).
Complete documentation deliverables: description, requirements, install & setup, test instructions.
Provide test vectors and automated tests where applicable.
Contact the Ledger integration teams (forms/contact addresses are provided in the Discover & Accounts docs).
Prepare backend endpoints for aggregator-style services (Buy / Sell) if relevant.

Resources (official)

Use these official resources during development and submission. The links are curated to the most relevant developer pages.

Next steps

Quick wins

Fork the Live App example, run Ledger Live locally, and prototype your signing workflow using the Wallet API. If you plan a blockchain listing, prepare the documentation checklist and contact the Accounts team early.

Questions to raise with Ledger

Which distribution channel (Discover vs Accounts) best fits our UX?
What are the exact submission timelines and legal agreements required?
Are there additional signing or metadata requirements for our chain or contracts?