Authenticating to Venly is done using OpenID Connect, which combines the OAuth 2.0 protocol together with a simple identity layer. We use OpenID Connect's Authorization Code Flow for our authentication and authorization.
🧙 An application requires a specific Client ID to connect to our environments. This not only improves security but also allows custom branding. To connect with a personalised Client ID, and access our production environment, please request access one using this form.
If you provide your own implementation of bearerTokenProvider, the web3 provider will not attempt to obtain an authentication code, but rather use the one provided by you.
In order to communicate with Venly, a Client ID is required. To connect to our staging environment and use the testnets, we provide a public Client ID Testaccount which is free to use and available to anyone.
The Client ID Testaccount only accepts requests from the following domains:
When you require access through your personal domain then please request a personalised Client ID by filling in this form.
To connect to our production environment and the different mainnets, a personalised Client ID is required. By using a Client ID that is linked to your application, an extra level of security is added, as it allows transaction filtering based on domain. It also allows for custom branding of the Widget.
In order to receive a personalised Client ID, and access our production environment, please request access one using this form.