🚀

Getting Started

There are multiple ways to integrate the Venly Wallet service into your app, depending on your goal, preferred type of integration, and desired UI flexibility.
In the table below you can find a comparison between the Wallet API, Venly Widget, and the different libraries you can use.
A detailed comparison between the Wallet API and the Venly Widget can be found here.
Web3 Integrations
Text
Description
UI flexibility
Networks
ClientId Required
Wallet API (RECOMMENDED for Backend integration)
A REST API that simplifies the interactions with a blockchain.
You are in full control of the UI/UX. You can build an wallet solution similar to the Venly Widget to onboard users. You will be responsible for integrating it with the different libraries.
13+ networks, including EVM and non-EVM ones
Yes
Venly Widget (RECOMMENDED Frontend integration)
A JavaScript SDK that wraps all the API functionalities and allows users to perform different blockchain operations.
The Widget provides out-of-the-box screens for the end users. They are not customisable.
13+ networks, including EVM and non-EVM ones
Yes
ethers.js
A JavaScript SDK that allows you to interact with an EVM client. It’s a standardised wrapper that provides access to the same functionality as the API.
Some of the calls (that require user interaction) would trigger the Venly Widget.
EVM-compatible networks
Yes
web3.js
A JavaScript SDK that allows you to interact with an EVM client. It’s a standardised wrapper that provides access to the same functionality as the API.
Some of the calls (that require user interaction) would trigger the Venly Widget.
EVM-compatible networks
Yes
web3-react
A JavaScript SDK, based on ethers.js.
Some of the calls (that require user interaction) would trigger the Venly Widget.
EVM-compatible networks
Yes
web3modal
A JavaScript SDK + UI components that allow you to connect user’s wallets to your application. Built on top of WalletConnect and wagmi.
The modal itself is customisable. If users choose to log in with Venly, the Venly Widget will be triggered on the different user actions.
EVM-compatible networks
No
wagmi
wagmi is a backend library that enables dApps to easily interact with Ethereum.
Gives developers full control over UI/UX (much like Venly’s Wallet API)
EVM-compatible networks
Yes

When to choose what?

If you want to build your own wallet app for users to interact with, you should use the Wallet API.
If you want to integrate an existing, full-fletched wallet solution, you can use the Venly Widget. There are multiple ways to integrate it - natively or by using another library (which also uses the Venly Widget in the background):
If you are new to Web3 and don't have experience with blockchain technologies, we recommend you use the Venly Widget natively for a better developer experience. If you have Web3 knowledge and/or already have experience with some of the other libraries that we support, we recommend you use those.
Another thing to take into account is the networks that you support and you want your users to be able to connect to. The Venly Widget supports 13+ networks, including EVM and non-EVM ones. The rest of the libraries only support EVM-compatible networks (with no specific implementations). Check Environments & Networks for more information.
And last, but not least - all listed libraries use Venly Widget in the background and it will be triggered on user action. However, for most of them, you have to build the front-end logic that will make it possible for a user to connect. There are libraries like web3modal that provide UI components for the wallet connection - you can use those in case you don't want to build this logic yourself.

Getting started with the integration

If you decide to integrate the Wallet API, make sure to check the Wallet API Documentation.
If you decide to integrate the Venly Widget natively, proceed to Getting started.
If you decide to use another Web3 library that supports the Venly Widget, check the Alternative Web3 Libraries (EVM networks only) section - it will help you get started and contains links to the relevant documentation.
​