Hi DavidK3 , regular support staff won't be able to help you ; you need to contact MYOB API support by lodging a ticket here (various information is required):
Submit a request – Support for the MYOB family of SME product APIs
There are many articles here:
Authentication, OAUTH and Authorization – Support for the MYOB family of SME product APIs
Also recommended:
Error Connecting 3rd Party App To MYOB 16-08-2024 – Support for the MYOB family of SME product APIs
Changes in the auth API – Support for the MYOB family of SME product APIs
The (truncated) value returned to your redirect URL will look something like this (you need to extract the highlighted section, other sections are explained in the above link):
http://desktop/?code=ory_ac_zTSXStega...Bel15h9uT8UUnc&scope=CompanyFile+offline_access+openid&state=fee7456fa62aef5f5ed486b6
Also note other users have provided code examples, eg:
C# WebBrowser -> WebView2 solution | MYOB Community
Hi DavidK3
Have you sorted your problem - Mike James gave some good pointers!
Likely I can help though most of my apps are based on MSAccess and this is really easy to fault find during development.
However I did then create a vb.net and vc.net test app successfully get my codes after the MYOB token server crash - reasoning - so I can sort for myself the problems.
Likely you are getting something back on your callback but not looking in the right place - as of the crash it is no longer embedded in the returned page but the returned url.
The red herring re the requirement for you to use a webbrowser2 was just that - a red herring - it wasn't the problem.
All my Access apps run perfectly without using a WebBrowser2.
Interestingly, XERO token codes creates an error in my MS Access trial app as "this browser is outdated" - but if I set errorflag=true to turnoff warning - I still get my codes without problem.
Regards
The Doc
