Introduction to file imports
Functional scope
The purpose of this collection of endpoints is to have products created or updated into the Neteven system via the use of a downstream, asynchronous Neteven service:
Instead of calling the API to directly create products via a JSON payload, the API is provided with a "standard" csv or XML flat file, which it forwards to the Neteven feed management system. In turn, this downstream system will read, adapt and import the file's content into the Neteven platform, through a pre-configured feed.
Why use a non-direct approach to product creation?
While at first glance, this seems to be a non-optimal way to have products created into the Neteven system, this multi-system design has the benefit of allowing Neteven better control over data:
- Import product information in bulk
- More flexible in terms of file structure (columns/fields can be named freely)
- Allows you to re-use pre-existing product feeds on your side
- Powerful content transformation capabilities via the flexible mapping tools
- Benefit directly from Neteven's expertise in terms of content management via mapping rules built specifically for you by a Marketplace publication expert from the Neteven team.
Flowchart
the below flowchart illustrates how the two systems (the Merchant API and the Feed Manager) interact in this process :
Requirements
To be able to create products with this method, you should first ensure the below actions have been done:
- the file you wish to send MUST be checked and validated beforehand by a Neteven Project Manager (one-time action, to be done during the initial integration phase)
- the Neteven Project Manager will confirm that the file is valid and can be used
- the Neteven Project Manager will set up a feed to process these files, and will give you the feed-id you should use when calling the merchant/products/import-file endpoint.