Update to MYOB Developer Program Terms and Conditions

A good idea - something XERO has already - no I am not pushing their access methods; it is just getting on-board as a partner there, required grasping scope as a standard part of an api call. 

It did my head in for a while, having gained my knowledge with the MYOB API calls - but likely, hopefully will make transition of my apps by Mar 26 easier.

A good Xmas project me thinks because Mar 26 will be here in a flash having now weathered 72 Christmases and their speed of transit from the end-of-the-year into the New Year.

The Doc

This is all a bit vague. I get that from March all my users will have to redo authorisation at least once every 12 months and I can send them an email telling them to do just that but at the moment all my apps are set  up for the old process.  Should I be telling them to redo authorisation before some date in March? 

I also get that I will need to amend my applications to replace the scope with a list of more specific scopes and the resulting authorisation will be for a specific company file as identified by a business Id/guid. If the users applies the app to more than one company file then the app will need to securely store authorisation details including business Id, code and refresh token specific to each file.

At present my apps get a company file list via the Companies end point and put it in a combo box so they can select the file. I gather that option will cease to be available so the company file selection will have to be from the above list generated via the authorisation process.

I am working on adapting the apps to do it that way but feel it would be nice if someone would provide a specific deadline for implementing this, preferably not too imminently. 

I have raised support tickets asking for more details and specifically this question and received no reply, only occasional snippets of information about how it will work being added to the online documentation. 

Hi eJulia​ , every app is different, but:

• note that only admin users can authorise from now on
• authorisation is file-specific; previously it applied to all files for which a user has access 
• MYOB will take care of prompts for renewals of authorisation
• the deadline is 28/02/26 (not 31/3/26)
• we've incorporated the necessary changes to our app
• we like not having to maintain a list of files
• we found the new oAuth process kinder/simpler in some ways, harder in others
• we've set up a default list of scopes per company that can be edited prior to authorisation (the feedback from MYOB during authorisation is quite generic). Our list is quite broad, to cater for all possible reports, but users can still choose to tailor it
• we've always stored file ID, access/refresh tokens per company
• we've advised users that an update is required by 28/02/26, and we're sending instructions
• we're preparing to support users who need help, expecting a busy week coming.

"

• we've advised users that an update is required by 28/02/26, and we're sending instructions"

That is the first I have heard of a specific deadline of 26/2/26! I have been storing a list of files including file Id based on the Company Files end point will/have to continue to do so for those users still not online. I will have to change code to bypass that process.

 For users with multiple files, it is not a matter like or dislike, it will be essential to create a list based on the files they have authorised. Some of them run automated batches of imports that import into more than one file so there is no possibility of a user being on hand to authorise each import.

Both the above date and the instructions should have been published months ago!

Thanks for sharing your knowledge on this one Mike_James​ 

eJulia​ , if you have any questions or need support, I would recommend getting in touch with the API support team.
You can create a ticket with them here

I have not seen the date 28/2/2026 in any official email from MYOB or on any online documentation, in fact this is the first time anyone has mentioned it and I have been looking all over for details like that and even asked the question in a support request, without getting an answer. 

The response to a support request raised before Xmas to specifically find out what was going on tended to suggest this was not an urgent panic. a response on 16/12/2025 said "The important point is that March 2026 is the enforcement date, not the point at which everything suddenly breaks. We'll provide more detail over the coming months, and existing integrations will continue to function until enforcement. In practice, this should be something you can roll into a planned release rather than a rushed hotfix." 

This is in line with the statement above from 3 monts ago "For now, there are no actions required. You’ll receive more information on dates and requirements for the API update over the coming months in 2026."

I have been trying to find out what "enforcement" means in this context but did assume it meant at least that users must re-authorise once every 12 months. I would also suspect that trying to authorise an old app from March onwards could be a problem but I had thought that I could count on the planned release route to the rushed hotfix.

I will be raising this again as a support request as there appears to be a problem with actually authorising mutiple files which would render the multi-file version of my app completely pointless.

Have resolved the multi-file issue but now want to know how to tell if a file is Aussie or NZ because that affects the files available. The only place I could find that info was in the Company Files endpoint. it is not in things like Company or Preferences and it affects what fields are available.

Mike_MYOB​ 

Above you said "You’ll receive more information on dates and requirements for the API update over the coming months in 2026." but have heard nothing specific since apart from some terrifying suggestions from unofficial sources that it will all fall in a heap next week.

Hi eJulia​,
There will be some communications sent out next week re the above. 
Rest assure, we are happy to work with you and all developers in regards to this change. 
If you want to, please book 15 mins to speak to us below. 

Book 15 min call with the developer team.