For Fireblocks’ recommended embedded wallet solution, see Dynamic Embedded Wallets. The documentation below covers the legacy Embedded Wallet APIs and SDKs.
Data Model

- User: Represents the end user of your application. Kindly note that this entity is external to Fireblocks and is reflected only on the customer’s side.
- Device: A logical identifier representing an entity that stores an end-user key share and can participate in MPC operations for a given wallet.
- Wallet: Represents an end user wallet created via the Fireblocks API.
- Transaction: Represents the transactions created in Fireblocks.
- Account: Represents the different accounts under a single end user wallet.
- Asset: Represents the different assets under a single account.
Relationships
- User > Device: One to Many relation
- Wallet > Device: One to Many relation
- Wallet > Account: One to Many relation
- Wallet > Transaction: Many to Many relation
- Device > Message: One to Many relation
- Account > Asset: One to Many relation
Device ID and wallet correlation. Each user can have multiple
deviceId values, each correlating to a different end user wallet in Fireblocks. Each deviceId represents an entity that stores an end-user key share.