Imports add data to eSales and is done by posting XML with an eSales Enterprise data type to the Web API. The XML must be encoded using UTF-8 and include the operations that is to be performed and all other data type related information. Allowed operations for imports are add, update, remove, and clear.

When importing data via the Web API, an Api-Key header is required for authentication. Only one data type is allowed per import.



URL format



Name Type Description Example
type string Type of import. Only one data type is allowed per import. See Import types
name string Optional name of the import. products-2017-09-06
import XML The request body in XML. See Examples

Import types

The following content types are allowed for the type parameter.

  • products (for products and categories)
  • panels
  • ads
  • synonyms
  • configuration

Read more about the import types and their file formats in the guide to working with imports.

Required headers

The header Api-Key is required.

Request body

An XML document containing the data to be imported, see Examples.

Request content-type


Response content-type

HTTP response code


Response Description
204 The import completed successfully.
403 Incorrect Api-Key.
404 Cluster not found.
4xx The request made by the client was invalid. This may mean that the import contained errors or that the cluster has not been defined prior the import. The response body may contain more information about the error.
5xx Server error such as cluster unavailable or busy. The response body may contain more information about the error.


Try out the API at the Apptus API Playground with your eSales Playground and API credentials.



<?xml version="1.0" encoding="UTF-8"?>
        <category_tree />
        <product />
            <title>The Magical Programmer</title>


curl -i \
-T products-full-import-w-variants.xml \
-H "Content-Type: application/xml" \
-H "Api-Key: {PRIVATE-KEY}" \


HTTP/1.1 204 No Content

This online publication is intellectual property of Apptus Technologies. Its contents can be duplicated in part or whole, provided that a copyright label is visibly located on each copy and the copy is used in conjunction with the product described within this document.

All information found in these documents has been compiled with utmost attention to detail. However, this does not guarantee complete accuracy. Neither Apptus Technologies nor the authors shall be held liable for possible errors or the consequences thereof.

Software and hardware descriptions cited in these documents might be registered trademarks. All trade names are subject to copyright restrictions and may be registered trademarks. Apptus Technologies essentially adheres to the manufacturer’s spelling. Names of products and trademarks appearing in this document, with or without specific notation, are likewise subject to trademark and trade protection laws and may thus fall under copyright restrictions.