Connectors and API calls with the Sales Layer PIM

For both the extraction and introduction of data to Sales Layer PIM using the Sales Layer API it is essential to have an Input connector or Output connector that acts as a regulator of the data exchanged with the corresponding Cloud account of Sales Layer. The connector will establish the exchange rules, act as a means of filtering and manipulating data, as well as mapping the Input/Output data.

Any requests made to the Sales Layer API must provide unique data from a connector (such as its security code and token), in order to achieve data extraction or manipulation tasks from a Sales Layer Cloud account. Therefore, it is necessary to have a Sales Layer client account, so the Incoming or Outgoing requests can be configured for the API.

In the Channel’s Marketplace section of the PIM cloud platform Sales Layer, there are several valid connectors capable of processing input/output requests through the API. The majority of these channels are specifically made for well-known third party applications, such as Magento, Prestashop, Adobe InDesign and Easycatalog, among others; these connectors are designed to connect via an API using either third-party software, or through plugins built for these platforms.

Conectores

There are also three open connectors dedicated to the extraction or insertion of data via API, shown in the image above. The Custom Connector and APPS Connector are used to configure access using the Data Extraction API (Output), whereas the Import Connector is for updating or inserting data (Input).

The purpose of this document is not to explain how to configure these connectors from inside Sales Layer. We also have an additional document with formulas and a connector manual for those who want to learn more about this topic. A common feature of these connectors is that they allow you to add multiple tokens or private access keys to secure calls via different applications that use the API.

Regarding the use of output connectors, another important feature is that they allow for the filtering of the items based on their status inside the Cloud platform, allowing different levels of granularity based on their visibility, as well as defining the aliases of tables to adapt the grouping format of the output.

As for the input connector, one of the most important features is that it allows for two different configurations: only updating existing records, or allowing for both updating current records, as well as inserting new records.