Skip to main content Skip to complementary content

Walmart Marketplace (Lite)

Walmart Marketplace is an online retailer company.

Supported update methods

For more information, see Change processing.

  • Change data capture (CDC)

  • Reload and compare

  • Change data capture (CDC) using Change Tables

  • Full load

  • Change data capture (CDC)

  • Reload

Preparing for authentication

To access your Walmart Marketplace data, you need to authenticate the connection with your account credentials.

Information noteMake sure that the account you use has read access to the tables you want to fetch.

The consumer channel type ID is a unique ID that you receive during your onboarding. It is used to track the consumer request by channel.

To get your client ID, you must create an API key:

  1. Log in to Walmart Developer Portal.
  2. Click My Account.
  3. Select the Login type: Marketplace or DSV.
  4. Create your client ID and secret from the API keys page.
  5. Generate a temporary token for your software. It expires after 15 minutes.
  6. Call the token API and specify your client ID and secret.

Creating the connection

  1. Fill in the required connection properties.
  2. Provide a name for the connection in Connection name.

  3. Select Open connection metadata to define metadata for the connection when it has been created.

  4. Click Create.

Connection settings
Setting Description
Data gateway

Select a Data Movement gateway if required by your use case.

Information note

This field is not available with the Qlik Talend Cloud Starter subscription, as it does not support Data Movement gateway. If you have another subscription tier and do not want to use Data Movement gateway, select None.

For information on the benefits of Data Movement gateway and use cases that require it, see Qlik Data Gateway - Data Movement.

Consumer Channel Type ID

Consumer channel type ID.

Client ID

Client ID.

Client Secret

Client secret.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!