From 1de7010425bba27a9927f96f6bc9ff010d8e1856 Mon Sep 17 00:00:00 2001 From: Ivan Dimitrov Date: Thu, 16 Nov 2023 10:17:43 +0200 Subject: [PATCH] wellsfargo case --- _content/cases/wellsfargo.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/_content/cases/wellsfargo.md b/_content/cases/wellsfargo.md index 817a03c..9d7cba6 100644 --- a/_content/cases/wellsfargo.md +++ b/_content/cases/wellsfargo.md @@ -26,4 +26,6 @@ For that reason I will not go into too much detail about the use cases as I'm no One use case documented on their website is the API Keys endpoint. 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.