Examples: query, "exact match", wildcard*, wild?ard, wild*rd
Fuzzy search: cake~ (finds cakes, bake)
Term boost: "red velvet"^4, chocolate^2
Field grouping: tags:(+work -"fun-stuff")
Escape special characters +-&|!(){}[]^"~*?:\ - e.g. \+ \* \!
Range search: properties.timestamp:[1587729413488 TO *] (inclusive), properties.title:{A TO Z}(excluding A and Z)
Combinations: chocolate AND vanilla, chocolate OR vanilla, (chocolate OR vanilla) NOT "vanilla pudding"
Field search: properties.title:"The Title" AND text
 
Answered
How to get Account Data Elements in an SSO extension

How would I go about obtaining the following pieces of information for accounts belonging to online users via the SDK in an SSO extension:

-interest rate (where applicable, ie for personal loans)
-length on file

Would you be able to point me to the appropriate docs or APIs for determining these pieces of information (preferably from the account_list that is accessible via SSO extensions, elsewhere if that's not an option). Thanks!

Posted 4 years ago
Ryan Hollister
196 × 4 Administrator
Votes Newest

Answers


These would be what we call "HostAccountDataElements" or "HADES".

Their presence will vary from one FI to another, also possibly vary from one product type to another. But they are available, unfortunately not on the incoming request. But a simple call will get you what you need. The data is returned in not such a great structure so just need to loop to get it into an easily accessible structure:

from q2_sdk.hq.hq_api.wedge_online_banking import GetUserAccountList

...
    account_params = GetUserAccountList.ParamsObj(self.logger, self.hq_credentials, True)
    accounts = await GetUserAccountList.execute(account_params)

    hades = {}
    for account_elem in accounts.json()['Data']['AccountListResponse']['Q2_AccountDataElements']:
        hades.setdefault(account_elem['HostAccountID'], {})[account_elem['HADEName']] = account_elem

This will leave you with a "hades" dictionary where the key is the host_account_id and the value is a dictionary where the "HADEName" is the key. (example dictionary attached).

So now for a given account you can lookup the meta-data we have for that account.

My recommendation would be to make the HADEName key's configurable so that we can set the associated HADENames you use differently per FI if for some reason they use different HADENames for Interest Rate or Origination Date.

But by default the HADENames you would be looking for are :

"IntRate" for Interest Rate.
"OrigDt" for Origination Date (yes even on non-loans)

Other HADENames can be found in Q2_HostAccountDataElement table

Posted 4 years ago
Edited 4 years ago
Ryan Hollister
196 × 4 Administrator
229 Views
1 Answer
4 years ago
4 years ago
Tags