Faster purchase bill retrieval in the Public API
We’ve improved the performance of the purchase bill endpoints when retrieving bills with many lines. This will help when you try to retrieve large numbers of bills more reliably. We are seeing average response times improve by 55% and P90 improvement is at 65%.
OAuth2 invalid_scope error for sme-* scopes
I'm running into an OAuth2 authorization issue. When I include any sme-* scope in the OAuth2 authorization request, the flow fails immediately with: The requested scope is invalid, unknown, or malformed. The OAuth 2.0 Client is not allowed to request scope 'sme-company-file'. If I omit the scope entirely, the flow succeeds but the resulting token only contains offline_access and openid. Example authorization URL https://secure.myob.com/oauth2/account/authorize?client_id=&redirect_uri=&response_type=code&scope=sme-company-file%20sme-general-ledger&prompt=consent What I've confirmed API key was created after March 2025, so SME scopes should apply Redirect URI is correctly registered — a mismatch returns a different, distinct error Tested multiple sme-* scopes — all fail with the same message Registered a brand new application and reproduced the same error Tested directly in the browser (no SDK or middleware involved) Old-style scopes (e.g. CompanyFile) also fail with the same error Any help is appreciated.
