Forum Discussion

Stuart_W's avatar
Stuart_W
MYOB Staff
4 months ago
Solved

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

Hi Everybody,

 

MYOB is strengthening its app ecosystem by upgrading integration endpoints to enhance data privacy and security. 

 

From 1 September 2026, all developers using the MYOB Business API will need to:

  • Update their integrations 
  • Adopt granular data scopes 
  • Ensure end users consent via the new flow 

Moving to granular scopes give developers more control over the data they request, making it easier to build integrations that deliver the best customer experience and take advantage of new features as they become available. 

What’s changing on 1 September 2026 

From 1 September 2026, the CompanyFile scope will be removed from the MYOB Business API scope list. Any new consent or authorisation request that still uses CompanyFile will fail. Developers will need to update their integrations to use the new granular data scopes.

 

To keep services running for customers, developers must ensure their applications request the appropriate granular scopes and that customers complete the updated consent flow. If these changes are not made by the deadline, affected integrations will be disrupted.

 

To avoid disruption to customer integrations or any impact on your developer program status, you must complete these updates by 1 September 2026.

 

More information about granular data scopes and the required changes is available below.

 

MYOB Business API Overview: Granular Data Scopes

 

If you have concerns about these timelines or need support to meet them, please submit a support request. If you’d prefer to speak to us directly, click here to book a time that suits you.

 

Thank you for partnering with us to improve data security, transparency, and customer trust across the MYOB app ecosystem. Kind regards, The MYOB Team

  • MarshallArts's avatar
    MarshallArts
    3 months ago

    Finally, I have an answer.  It is necessary to create your own instance of a CompanyFile object in code, rather than getting it via the (soon to disappear) CompanyFile Service.  So, after authentication is complete and you have your businessId value, the following steps (in C#) worked for me:

     

    1. Make a Guid object, and populate it.  myBusinessID is the string value of the business ID
      Guid myCFGuid = Guid.Parse(myBusinessID);
    2. Declare a CompanyFile object, and create the instance
      CompanyFile myCompany;
      myCompany = new CompanyFile {
          Id = myCFGuid,
          Uri = new Uri($"https://api.myob.com/accountright/{myCFGuid}")
      };

      This code creates the CompanyFile instance, and initialises the Id and Uri members.
      That appears to be all that is required.  You could also collect the Business Name and set that if you wanted.

    This CompanyFile object can then be used as the first parameter to the Get/GetRange calls to the various Service objects that request data from the MYOB cloud.  And the other calls for updating etc no doubt.  So simple once you see it.  I hope this might save someone else the hours I have burnt trying to figure this out.

39 Replies

  • NathanCrane's avatar
    NathanCrane
    Experienced User
    1 month ago

    Never mind, chalk one up for yourself. Of all the silly mistakes to make, I had a typo in the prompt=consent part of the request, so it was abiding by the old rules.

     

    I registered a test app with the company's https homepage as the url and that worked out for me. 

  • I'm having an issue today with this update.  I have posted on the community page with the title API issue with importing from simPRO to MYOB AR - nobody has responded, can you help?

  • Will the old API keys all be invalid after the 1st? I wasn't aware API keys required activation until finding a note deep within the documents. Even though the API key worked with the auth flow.


    I've contacted support 7 days ago (case number 51973), but still waiting to get it activated.

  • NathanCrane's avatar
    NathanCrane
    Experienced User
    1 month ago

    When did they slip that requirement in? That would explain my troubles with my new test key neatly. 

     

    I'm in the same boat as you as far as support tickets go, cannot get a reply for love or money right now. 

  • kirsten's avatar
    kirsten
    Trusted User
    1 month ago

    I am in such a world of pain on this. I see the 15 minute help slots are booked out for a week.
    My redirect url is http://localhost:5001/callback
    I see in the example here it starts with https 
    However I still have a client able to post invoices with the old url.
    I know it is important that it matches what I have in the registration but does it really need to start with https? 

  • ROC_MYOB's avatar
    ROC_MYOB
    MYOB Moderator
    1 month ago

    Hey JasonSynsoft​ , 
    Ive added this to backlog of API improvements. 
    We are currently looking at the Developer Portal and improvements. 
    Thanks Ryan

  • ROC_MYOB's avatar
    ROC_MYOB
    MYOB Moderator
    1 month ago

    Hi DavidDNCS​ 
    I can take a look at where the emails for your app are sent too. 
    If you want me to take a look at it please let me know. 
    Thanks 
    Ryan

  • ROC_MYOB's avatar
    ROC_MYOB
    MYOB Moderator
    1 month ago

    Hey kirsten​ , 
    Are you still seeing the 504 error? 
    I can organise a 15 minute call if needed still. 
    Thanks
    Ryan