This article has moved to a new home. View the updated version

How can I push data to or pull data from Neto? APIs and FTPs

There are two ways to get data from and push data to the Neto platform:

  • API
  • FTP File Drop / Pickup

API Method

The Neto application programmer interface (API) enables third party software to interact with the Neto Digital Commerce Platform. Currently all transactions are performed via HTTPS POST.

You can Add, Update, Delete and Get data using the API.

We are intent on continually updating and improving the API in it’s current release. There are functions not available through the API and until such time as we have made all functions available the API will remain in development.

Getting Started:

1. Get Setup

  • Signup for a free Neto trial account
  • Generate an API key (From the Neto Dashboard, select Setup & tools​ > Users​ > Select the User > Generate API)

2. Explore

3. Build

  • Build your integration
  • Checkout our recommended workflows for different app types
  • Ask us if you get stuck, require additional fields, calls or advice

FTP File Drop / Pickup Method

Neto can pickup data from and put data files into any FTP location. The following data can be imported / exported this way.

  • Orders and Order lines
  • Shipping Tracking Information
  • Customers
  • Products / Inventory

Exporting Data

Neto has the ability to create export files in any flat file format including .xml, .csv, .txt etc. These files can be built on the fly using the export file builder which supports our tag and function library. All available database fields can be used in export files. Once created, an export file template can be used for future file creation.

Importing Data

Neto has the ability to map to practically any flat file format including .xml, .csv, .txt etc. Once mapped a mapping template can be created and used for future import of files in the same format.

Importing and exporting of data can happen at a pre-defined schedule or processes can be run manually. For example, you could have the import system set to pickup an order file every 15 minutes from a set FTP location and then move the file to an archive folder once processed.

Example work flow 1 - Adding / Updating Products

Set up an import template to import a product file.

  1. The product file would contain information such as SKU, name, description, price and image URL.
  2. The import template would be setup to “add new / update existing” products.
  3. Setup a schedule to poll an FTP location periodically to pickup and process the product file data.
  4. Once created, set the system to archive the product file in an archive folder.

Example work flow 2 - Adding Orders and Exporting Tracking Information

  1. The order file would contain order details such as order ID, address information and order line data.
  2. The import template would be setup to “add new” orders and “ignore” duplicates.
  3. Once processed, set the system to archive the product file in an archive folder.
  4. Once created, orders would be processed and dispatched using the Neto platform.

Example work flow 3 - Setup an export template to export order dispatch notifications.

  1. The dispatch notifications file would contain tracking numbers related to dispatched orders.
  2. Setup a schedule to put the dispatch notification file at an FTP location periodically.
  3. A 3rd party system would then access this location to get the dispatch notification files to update its own systems.
  4. Unique identifiers such as Order ID and product SKU would be used relate data between the two systems.

Was this article useful?

Be notified when this page is updated. Optional.

Last Modified: 28/09/2017 Neto Version: 6.3