Dear WealthLab Team,
I am currently working on an integration into your product.
Although I am relatively new to the stock market environment, I am committed to learning the necessary terminology.
Your online help and the example on GitHub have been helping tp facilitating a rapid initiation.
However, I have noted a significant missing of the XML documentation file, used to IntelliSense in visual studio.
On reviewing the public members of your API DLLs, I found that none of the methods are documented. Furthermore, I have encountered several methods that are neither covered in online searches nor in WealthLab's own developer documentation.
Please excuse my english i am no native english.
Best regards,
Mike
I am currently working on an integration into your product.
Although I am relatively new to the stock market environment, I am committed to learning the necessary terminology.
Your online help and the example on GitHub have been helping tp facilitating a rapid initiation.
However, I have noted a significant missing of the XML documentation file, used to IntelliSense in visual studio.
On reviewing the public members of your API DLLs, I found that none of the methods are documented. Furthermore, I have encountered several methods that are neither covered in online searches nor in WealthLab's own developer documentation.
Please excuse my english i am no native english.
Best regards,
Mike
Rename
Sounds like a large effort to document lesser used APIs. And what precisely is missing? That you couldn't find covered in the already extensive documentation?
https://www.wealth-lab.com/Support/ExtensionApi
https://www.wealth-lab.com/Support/ApiReference
https://www.wealth-lab.com/Support/ExtensionApi
https://www.wealth-lab.com/Support/ApiReference
Hi Eugene,
ty for your quick reply.
one i found was the PerformOAuth method sitting at hte ihost interface.
although i am familiar with open authentication it is not clear to me what is going to happen here? my guess is the authurl parameter is the /connect/token endpoint, the client name is the client_id and the matchurl probably the return_url you capture.
Are there scopes send along the auth request?
My integration approach is creating an extension menü where the customer can login and only then make the dataset and eventproviders available. but i have not found out yet how i can dynamically trigger refresh to the datasetprovder.
i will open another thred to go deeper into that question.
Thank you
Mike
ty for your quick reply.
one i found was the PerformOAuth method sitting at hte ihost interface.
although i am familiar with open authentication it is not clear to me what is going to happen here? my guess is the authurl parameter is the /connect/token endpoint, the client name is the client_id and the matchurl probably the return_url you capture.
Are there scopes send along the auth request?
My integration approach is creating an extension menü where the customer can login and only then make the dataset and eventproviders available. but i have not found out yet how i can dynamically trigger refresh to the datasetprovder.
i will open another thred to go deeper into that question.
Thank you
Mike
Your Response
Post
Edit Post
Login is required