Great question. ReadAuthorizationStatus should ideally provide a means to determine this information through the scope field / sub-element of the AuthorizationStatus element, via the "HistoryLength" ValueTerm. At present, however, the Test Lab does not provide return this information in a response to this service call. We will investigate further.
Please don't investigate for too long or make a decision that this is it for the contest. I would like to finish an app and don't have to monitor your changes for another 2 month. Do you think it is possible?
There is a problem. Regardless of what I specify in history length I get 730 days in Read Authorization status and then when I try to get the data I get "Bad request". Can it be that you are taking this value from your portal third party app and I do authorization from mobile device? Example I specify 100 history days and I get bad request when I ask for July 2013 but my auth status reports 730 days.
Yes thank you. This is currently being investigated. The HistoryLength should indicate how much hstory data your application has been authorized to retrieve by the Customer. It would seem, however, that the Test Lab is reporting the maximum value it supports instead.
If you don't fix that my app will have a problem to correctly calculate what data can be requested if user allows less than 2 years of data. The user will get "bad request" instead of getting available data.
"The functionality to get the value from what was specified by the Customer during the authorization process has not been implemented in the test lab. The maximum value of 730 was [initially] enough for testing."
If we are able to add functionality to the test lab we will do so. If not, the apps will be judged with its limitations in mind.