Currently we allow an application to be defined in a single QuickFile account and for that application to call other QuickFile accounts with the appropriate API credentials (Account number and API key). From 4th September 2017 this will no longer be possible and an application will be restricted to making calls only to the account within which it is defined.
There are two solutions that you may wish to consider here:
##1. API Partner Programme
The API Partner Programme was designed specifically for applications that require the ability to interact with multiple QuickFile accounts. The benefits to using this system are twofold, firstly we will provide a platform for you to promote your application to other QuickFile users on the new Marketplace area.
Secondly the Marketplace makes it easier for the end user to only grant specific permissions for a 3rd party application and revoke them later, as they see fit. If a user wishes to connect to your application we will generate a token that they can use to grant access through an intermediate API call.
You can find out more about the API Partner Programme here.
##2. Setup an Application on each target account
If your application only requires access to a few accounts and you have no need to promote this application to other users, you can continue using your existing implementation by simply setting up an application profile on each target account. You will then need to ensure that you are passing the appropriate ApplicationId for each respective account.
Please note: these restrictions will be implemented along with the XML API endpoint change on 4th September 2017.