Reminder: Update your MYOB Business API integrations by 1 September 2026

DavidDNCS​ , there is no other option, to authorise file access you must be a file admin. Your client can give you that role temporarily, and even make your file access read-only until authorisation is complete. (The authorisation from your app will still work).

That error message could also relate to an invalid redirect. There are much stricter rules about redirects now, as the API support write to me:

“validation of the redirect URI has been tightened. As a result, non-HTTPS, localhost-style, or internal hostnames (like http://desktop) may now be rejected during the final redirect step after consent. When that happens, it surfaces as a generic “unable to connect, something went wrong” message, which is what you were seeing”. (This strict application was not notified.

Hi MYOB Developer Team

I have just become aware of this issue.  I do not seem to be receiving any important updates from the MYOB Developer team, does MYOB actually email the MYOB Developers registered email addresses about really important changes to their API ?  I have searched through my emails and cannot see any communication about this.  I fortunately was reviewing my post and also posting a new issue when I came across this but would have loved to know about it in November 2025 which it was launched. 

Just getting my head into this.  I've made the changes to my app's authorisation URL and I do get the MYOB page come up that spells out what is being requested and invites the user to Connect.  But when I do that I get a message that says "Something went wrong and we couldn't connect the app".  Below that it says that I need to be an administrator on the company file to be able to connect.  I'm not an admin and I'm not sure my client would want me to be an administrator - is there some mechanism in place to enable testing and development?  Is this this app connection is a one-time thing, or will it happen every time?  Can I do something in my developer account to get me past this?  The app in question is registered in my account.

Hi cas-tag​ that is correct. Authorisation is for one file now, which is selected after submitting a request and being prompted to log in with your email/password. You must have the file admin role to authorise.

Currently with my.myob acting as OAuth - the auth that is provided is for the User, and thus the resources returned available for accesss are ALL companies the user has permissions for.

In the case where a my.myob user has access to multiple companies - are they required now to select a specific company, and the code/auth returned then is only for that 1 single company, not for all companies that the user has access to (an OAuth resource flow not a user flow)?

Hi Trish,

Yes, the granular consent model is already in place, so we would recommend updating your apps as soon as possible. If you have any questions on the new granular scopes or other issues, please submit a new support request below:

MYOB Business (AccountRight) API Support Ticket Form

Hi Stuart, 

Well, done on getting this out there so early :-) Is this already in place so that I can test and start releasing to Clients?

Thanks

Trish