Hi benjharvey01
What language are you using?
I haven't heard of Nango - had a quick look but I think it will work so long as you keep up with Nango - came across a freebee - a client who ghosted me in 5 minutes because I wouldn't supply my api access codes and secret with the bulldust he pedaled did actually send me a program written in Access that he was trying to get access to the MYOB API - it was a jumble but it used a still going freebe app which looked interesting... I will try and find - not accessible immediately.
For myself I started accessing the MYOB API 10 years ago and MYOB had VB.NET and C#.NET trial code to get you going with their SDK - I got the VB.NET working with my app but never got the VC# one working.
However, most of my app are developed in MS Access and MYOB never wrote trial code for Access access - I looked at writing a hook to some VB.NET code but shelved that and just wrote all my own code to access the API, manage the codes and to get and decode and post JSON to and from the API.
This code - which is all my own - and the ability to alter any part of it when MYOB's API crashes has enabled me over the years to be little affected by the changes in API access - it just keeps working.
When the big crash happened in Aug 24 - it took a while to identify the problem - only because MYOB tech didn't know arthur from martha about what had changed - once I idented the problem the code change to get up and going was so small as to be laughable or cryable.
My point - write your own - it will take a bit of work but will enable you to always be ahead of changes - eg. the change coming 1 Sept with scope I have tested already with a test app - and hopefully will just be a minor code change on authorize in the getting of the initial access code on a completely new data call - and shouldn't affect just refresh calls - fingers crossed.
The Doc
