The SOAP API allows you to update and read many fields on orders, purchase orders and articles. In our experience, very few integrations need to use these entities. It is unrelated to the "shipments" which transporters such as DHL and UPS have) Shipment (note: this refers to Ongoing WMS' own concept of a shipment.The following entities can only be managed using the SOAP API, and not by the REST API: May read shipments and production orders 1Īllows the API user to read and update a large variety of data fields on the orders, purchase orders and articles 3Ĭan create kit articles and production articles 4Įach order and purchase order must have a unique order number 6Įach article must have a unique article number 7Īllows detailed advising of goods information on purchase orders 8 May read both the current and historical stock balances May read tracking information from orders May attach files to orders, purchase orders and articles May create, update and read articles, orders, purchase orders and return orders Here are some specific comparison points between the APIs. Thus, the SOAP API has more functionality, and the REST API is easier to use. The REST API is a smaller and more focused API where the API user is offered less choice in how the integration works.The SOAP API is a large and extensive API which gives the API user wide latitude in how he wishes to control Ongoing WMS and which fields to use.
The key difference between the two APIs is: In this article we will explain the difference between the Goods Owner SOAP API and the Goods Owner REST API. We also have an automation API which is used when you wish to connect automation equipment like conveyor belts. Goods Owner REST API - based on Representational state transfer.Goods Owner SOAP API - based on Simple Object Access Protocol.Ongoing WMS has two different Application Programming Interfaces (APIs) which are intended for connecting systems like business systems (ERPs) and web shops to Ongoing WMS:
0 kommentar(er)
