Sales Layer has a web service that meets the standards of the REST architecture. This service is accessible throguh this url.

The web service, which from now on will be referred to as the API, allows us to extract from, and enter information to a Sales Layer account via third-party services, such as a web application, mobile app, data mining applications, and more. The extraction or introduction of data to Sales Layer via the API requires the configuration of at least one Export connector (for data extraction), or an import connector for data entry. The connectors must be secured using a token, which can be obtained directly from the Sales Layer cloud platform. The requests through the API will be made with the connection and security parameters, which are described later in the “Cloud” side of Sales Layer. The extraction responses, as well as the data that can be introduced, is always dependent on the configuration made in the corresponding connectors on the Cloud side of the PIM.

The following graphic shows the API request architecture.

Arquitectura de peticiones

As the Sales Layer API is a RESTful web service, it is possible to exchange data with the Sales Layer cloud platform, using different programming languages. The exchange of information uses Javascript Object Notation (JSON), a data representation structure widely used in this type of web services and one which is well supported by most popular programming languages including Java, JavaScript, PHP, C, Python, etc.

The Sales Layer API also allows you to obtain output data in Extensible Markup Language (XML) format.

Sales Layer Rest API works transfering the whole catalog as delimited by the channel. That allows to easily replicate all the info in the target where it’s going to be used with an optimal performance.

Sales Layer provides an SDK (for now, available only in PHP) to allow automation of this process of data replication in an easier way. 


Our API is configured to send all the changes made in Sales Layer, even if they are not included within the connector filters.

For example, if we configured a connector to export only Visible items and we modify Invisible or Draft products, the API will return these changes and send ones related to the Invisible and Draft items as "Deleted".

As a result:

If our connector is configured to export only visible products and we change the status of a product to Invisible, the API will send it to be deleted.

If we filter by tags in a connector and we remove the tag from a product that was previously being sent, the API will send it to be deleted.