Forum Discussion

Mike_MYOB's avatar
Mike_MYOB
Community Manager
2 months ago

Update to MYOB Developer Program Terms and Conditions

We’re making some changes to the MYOB Developer Program and Platform Terms and Conditions. MYOB is strengthening its app ecosystem by upgrading integration endpoints to bolster data privacy and security.

 

View the updated Terms and Conditions

 

From March 2026, all developers using the MYOB Business API will be required to:

  • update their integrations;
  • start using granular data scopes; and
  • ensure their end users re-consent to data sharing

 

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.

 

If you would like to fast track the update, you can find more information about granular data scopes and what’s required below.

 

Learn more

 

These updated Terms will come into effect from 19 December 2025

3 Replies

  • The_Doc's avatar
    The_Doc
    Ultimate Cover User
    2 months ago

    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

  • eJulia's avatar
    eJulia
    Trusted User
    19 hours ago

    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. 

  • Mike_James's avatar
    Mike_James
    Ultimate Cover User
    23 minutes ago

    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.