Ledger Live Integrations – Ledger Developer Portal

A practical guide to integrating apps, blockchains and services with Ledger Live (Ledger Wallet). Includes recommended workflows, SDK/Wallet API notes, submission tips and quick code snippets.

Why integrate with Ledger Live?

Integrating with Ledger Live (the Ledger Wallet ecosystem) gives your project access to millions of users who trust hardware-backed key security. Integrations can be at multiple levels: add a blockchain to the accounts list, offer in-app services (swap, buy, sell), or create Live Apps (dApps) that run within Ledger Wallet.

High-level integration paths

1. Blockchain account integration

Add native account management so users can view balances, send/receive and sign transactions through their Ledger signer without exposing private keys.

2. Live Apps (dApps)

Live Apps run inside the Discover/Live Apps area and talk to the Wallet API to request account info, prepare transactions and trigger on-device authorization flows.

3. Services & Providers (Buy/Sell/Swap)

Integrate a service provider via the dedicated integration endpoints so users can compare and use your services inside Ledger Wallet.

Core tools & docs (bookmark these)

Below are the official developer resources you should keep handy while building — they contain SDKs, Wallet API reference, app submission checklists and device interaction guides.

Use the Wallet API for Live Apps and the SDK snippets in the portal for local dev flows and device interactions. The submission checklist explains required docs, install instructions, and testing expectations before your integration can be published.

A quick architecture: how Live Apps talk to Ledger Wallet

Live Apps use a controlled channel (Wallet API / Services Kit) that lets the app ask Ledger Wallet for account metadata, construct transactions and request the user to confirm the action on their device. Private keys always remain on the Ledger signer — Ledger's architecture is designed so signing prompts are human-readable and require device confirmation.

Example: prepare -> preview -> sign

App requests account list & nonce from Wallet API
App prepares a transaction payload locally
App asks Wallet API to trigger user confirmation
Ledger Wallet displays transaction summary and the user confirms on-device
Signed transaction is returned and broadcast by the app or Wallet

Minimal Wallet API code sample

The example below demonstrates the basic flow using the official Wallet API client library. Replace placeholders with your Live App values.


// Minimal pseudocode / JS (conceptual)
import { useWalletClient } from "@ledger/wallet-api-client";

// get client (React hook / client)
const client = useWalletClient();

async function sendTransaction(accountId, txPayload){
  // 1. request account info / permissions
  const account = await client.getAccount(accountId);

  // 2. prepare transaction (app-specific)
  const prepared = prepareTx(account, txPayload);

  // 3. ask Ledger Wallet to trigger signing
  const signed = await client.requestSign({
    accountId,
    rawTx: prepared.serialized,
    humanReadable: prepared.humanReadableSummary,
  });

  // 4. broadcast signed.txHex via your chosen node/provider
  await broadcastSignedTx(signed.txHex);
}

Tips

Always provide a clear human-readable transaction summary — device UI space is limited.
Keep sensitive logic on your servers or in the app — device only signs what it's shown.
Prefer readonly scopes for account queries; request write permissions only when needed.

UX & security best practices

Design for trust

Users trust Ledger because private keys are hardware-protected. Your integration should not undermine that trust: show clear descriptions, show amounts and recipients, and avoid hidden fees or ambiguous labels.

Testing & developer mode

Ledger provides developer-mode guides and local dev workflows. Use testnets and the recommended dev tools before requesting an official listing — incomplete or untested integrations will be rejected during review.

Submission checklist highlights

Clear documentation & install steps for your app.
Security expectations and how you handle user data.
How to reproduce common flows (receive/send/stake/swap).

Publishing & maintenance

After building and testing, follow the Developer Portal's submission flow to request an agreement and review. Ledger runs reviews that include technical checks, UX checks, and security assessments. Expect to provide install instructions, test accounts, and contact details for maintenance.

Ongoing maintenance

Keep endpoints, manifests and SDK versions up to date. Notify Ledger when you change critical flows (e.g., signing format, endpoint changes) so integrations remain reliable for users.

Next steps

Start by exploring the Wallet API docs and the Live App tutorial, spin up a local dev environment, and build a simple send/receive flow. When ready, follow the submission checklist and reach out via the Developer Portal forms to request an integration review.

Open Ledger Developer Portal