Thanks, but it's not the authorisation phase that is the problem. I think I have that working now. It's requesting data once I am connected. In the .NET SDK there are Service objects which basically wrap the various endpoints with a .NET object. I make calls on those Service objects to request data.
The SDK basically consists of .NET objects which wrap the endpoints. Only during the authentication phase does the developer need to work directly with URLs - after that it is just calls to methods on the many objects in the SDK. The calls which request data all have as their first parameter a CompanyFile object, which is derived from the CompanyFile endpoint. There is also a CompanyFileCredentials object passed to each call. If the CompanyFile endpoint is about to disappear, then it seems to me that the SDK needs a complete rework in order to make it usable with the new granular scopes. It will need to be able to work somehow via the businessID instead, but I see no sign that any such rework is in progress. If I can't use the SDK it will be a large task to rework my integrations using a completely different approach.
I started out many years ago with SDK code supplied by MYOB. In its CompanyFIle service the GetRange option no longer works but Get.CompanyFileWithResources using the id passed back with the BusinessId passed back with the authentication worked for me. once I had that timing sorted (await the authentication) then get the tokens using the code that comes back (wait for it) and then ensure that a token refresh occurs before asking for that record it all seemed to work well for a while.
