Learn how to enable your customers to go through Groov's Connect consent management journey (white labelled with your brand) and connect their external accounts
Connect
Draft,....
In the Integration section, you’ll find access to the user secret_key. The user secret_key is used to authenticate your application against the Groov API and should be treated confidentially. We dont expire the user secret_keys at the moment but if you loose them, you can regenerate them on demand by reaching out to us. The institution client_id is not secret but is used to identify your application instance with us as an institution, this can be found in the Developers section (which is under design).
The Integration section also allows you to configure redirect URIs. Groov's Connect consent flow (and SDK's) will redirect to one of these URIs when your customer authorises the account consent with Groov, we will not be able to redirect to any other locations. These redirect URIs could be as simple as your application page details from where you initiated the Groov Connect consent flow (or could be as simple as to your institution web page if the consent initiation at your end has been via a manual campaign). Currently our default setup allows you to provide one redirect URI.
Flow
Draft.....