Article ID: 128383, created on Feb 19, 2016, last review on Feb 19, 2016

  • Applies to:
  • Business Automation


AccountAdd_API fails with "Access Denied" exception.


There are several possible reason for such issue:

  1. The user under which API call is made does not have the privilege ACCOUNTS_CREATE_MODIFY in his role.
  2. The user under which API call is made is not a staff member of the VendorAccountID specified in the call (e.g. the resellers staff member attempts to create an account for the provider).
  3. Incorrect call structure, for example, the first optional parameter AccountID is passed as int and the system considers this parameter as a VendorAccountID. As a result the system checks if the user under which the call is made is a staff member of this VendorAccountID and it results in Access Denied.


  1. Either add a privilege to the role or use a different user.
  2. User a vendors staff member to execute a call.
  3. Correct the structure according to the documentation, AccountID is to be passed as string, e.g. <value>AccountID=100025689</value>.

198398b282069eaf2d94a6af87dcb3ff caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF