Integrating with Neto

There are limitations to the Neto API in which the Update Order API cannot write certain fields and cannot perform certain functions.

Core limitations of the Neto API:

• It cannot do backorders.

  It understands marking orders as shipped, but does not consider shipped quantities.

• It cannot write back serial numbers.

  Go to the Manual Update section for details.

• There is no API for any Neto advanced inventory functionality. All functions are emulated through a screen grabber macro tool.

For .wms to communicate with Neto, authentication must be set up.

Neto uses the associated Username / Password or Key set up in the headers of our calls. It can therefore, authenticate in 2 methods:

• API User / Password - an API user must be created with a password and the details forwarded to the Thomax Project Manager to confirm authenticity.

or

• Global API Key - in the Neto control panel, go to Settings & Tools > All settings & tools > API.

Neto also has an OAuth methodology for connections. This method is not as stable as a simple API Key and is therefore not recommended. It is supported by Thomax and .wms, if this method is to be used.

Coordinate with the client's Neto administrator and the Thomax Project Manager to set up an OAuth connection. This must be done together with our implementations team so as to get the access tokens at the correct time. This is important as the access tokens expire.

For all data sourced from Neto, .wms works on a scheduled Pull task. This applies to sales orders into .wms, item data into .wms and purchase order data into .wms.

For all data going back to Neto, .wms works on a Push task. This means that the data is attempting to write back immediately.