Skip to Content

Magazine Luiza Shopping Connector


The Jitterbit Harmony Magazine Luiza Shopping Connector establishes access to Magazine Luiza Shopping.

The Magazine Luiza Shopping connector provides an interface for creating a Magazine Luiza Shopping connection, the foundation used for generating instances of Magazine Luiza Shopping activities. These activities, once configured, interact with Magazine Luiza Shopping through the connection.

The Magazine Luiza Shopping connector is accessed from the design component palette's Connections tab (see Design Component Palette).

Connector Overview

This connector is used to first configure a Magazine Luiza Shopping connection. Activity types associated with that connection are then used to create instances of activities that are intended to be used as sources (to provide data in an operation) or targets (to consume data in an operation).

Together, a specific Magazine Luiza Shopping connection and its activities are referred to as a Magazine Luiza Shopping endpoint:

Magazine Luiza Shopping activity types

  • Read: Retrieves object data from Magazine Luiza Shopping and is intended to be used as a source in an operation.

  • Create: Creates object data in Magazine Luiza Shopping and is intended to be used as a target in an operation.


This connector is a Connector SDK-based connector, which may be referred to by Jitterbit when communicating changes made to connectors built with the Connector SDK.

Prerequisites and Supported API Versions

The Magazine Luiza Shopping connector requires the use of an agent version 10.1 or later. These agent versions automatically download the latest version of the connector when required.

The Magazine Luiza Shopping connector uses the Magazine Luiza Shopping REST API. Refer to the API documentation for information on the schema nodes and fields.


If you experience issues with the Magazine Luiza Shopping connector, these troubleshooting steps are recommended:

  1. Ensure the Magazine Luiza Shopping connection is successful by using the Test button in the configuration screen. If the connection is not successful, the error returned may provide an indication as to the problem.

  2. Check the operation logs for any information written during execution of the operation.

  3. Enable operation debug logging (for Cloud Agents or for Private Agents) to generate additional log files and data.

  4. If using Private Agents, you can enable connector verbose logging for this connector using this specific configuration entry of logger name and level:

    <logger name="org.jitterbit.connector.verbose.logging.magazineluiza" level="DEBUG"/>
  5. If using Private Agents, you can check the agent logs for more information.