[Wells Fargo](https://www.wellsfargo.com/) is a US based international financial institution operating in 35 countries and serving over 70 million people worldwide.
Integrating Open Banking APIs requires many security and legal precautions. There is always a double layer of encryption for all APIs and communications (even emails).
[mountains of documentation provided by the bank](https://developer.wellsfargo.com/guides/user-guides/open-banking-europe-api-integration/obei). For that reason I will not go into
too much detail about the use cases as I'm not sure what I am allowed to talk about.
To generate an API key you need your client credentials with a key and a secret in this format `Authorization: Basic base64(consumerKey:consumerSecret)` as well as the scope in the
form `grant_type=client_credentials&scope=accounts`. There are hundreds of scopes to configure. This gives you an `access_token` which is valid for 24 hours, has the scopes
(permissions) you requested and is used for most API communications.