Ongoing WMS Automation API
Apart from the regular goods owner SOAP API and the goods owner REST API, Ongoing WMS also exposes a more advanced API called the automation API. This API allows an external system to perform certain internal warehouse operations, like moving goods from one location to another.
Most API users will never need this functionality, but it is crucial when integrating with automation equipment. Because of the custom nature of such equipment, you may have to consult with Ongoing WMS before beginning implementing your integration.
Differences between the goods owner SOAP API and the automation API
- Out of necessity, the automation API exposes a lot of internal details about Ongoing WMS. For instance, in the goods owner SOAP API an article is generally referred to by its article number, but in the automation API we use Ongoing WMS' internal article definition id instead.
- When calling a function in the goods owner SOAP API, you generally have to specify which goods owner you want to work with. In the automation API, this is usually not required. The automation API allows you to work with all goods owners.
- The goods owner SOAP API has its endpoint at Service.asmx, while the automation API's endpoint is Automation.asmx.