AccountsIQ SOAP API Update Bulletin (23 02 2023) - accountsIQ/API-Wiki GitHub Wiki
Welcome to the API update bulletin!
You are receiving this as a registered user on our API who has opted in during your initial setup. This bulletin will notify you of any changes, additions and bug fixes made to the API in general.
These changes should not affect existing integrations. An update will only be required if you wish to take advantage of the new methods or fields added, unless otherwise stated.
Please refer to the API wiki for more details on the API, and contact us if you require a Postman Collection to be sent to you.
Changes are:
Reject Inactive BI Codes/Departments
Status: Released Type: Bugfix
Some methods receiving BI Codes/Departments IDs were not checking for inactive records correctly, causing invalid values to be registered against different transactions, such as Invoices, Orders, Credit Notes, etc.
Examples: One of our integrators had item invoices submitted through a 3rd party system, which included inactive BI Codes for the invoice lines. However, the invoices were created successfully.
New property, ExchangeRate, has been added to the different Get Transactions methods
This new method will work similarly to GetTransactionsBy, which returns pages of 10k rows max. The existing method GetOrdersBy doesn't implement paging, which was causing the entire data set of Orders filtered by the query to be returned.
Examples: Some clients with a massive amount of orders were experiencing issue calling GetOrdersBy as their query was too broad, making the API to try and return all the rows in their database table, which was causing a timing-out and returning NULL instead.
This new method will receive a CurrencyCode and return the historical records of changes for this particular currency.
Examples:
New API methods added - Delete a Customer or Supplier, by its ID or Code.
Status: Released Type: Enhancement
Our External Integrations Team needed a way to delete suppliers and customers, in the same way a user could do from the UI.
Examples: On occasion when running workflows involving creating customers/suppliers, things can go wrong, resulting in many copies of the same customer/supplier, which will be left in the system without use.