Walmart

Walmart is a multinational retail corporation operating a chain of hypermarkets, discount department stores, and grocery stores, providing sellers and partners with tools to manage inventory, orders, and marketplace operations.

Power end-to-end data operations for your Walmart API with Nexla. Our bi-directional Walmart connector is purpose-built for Walmart, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Walmart or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Walmart workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

Before creating a Walmart credential, you need to obtain your Client ID and Client Secret from your Walmart Developer account. Walmart uses Basic Authentication for all API requests, with the Client ID and Client Secret used as username and password.

To obtain your Walmart OAuth credentials, follow these steps:

1. Sign in to your Walmart account using your administrator credentials.

2. Navigate to the Walmart Developer Portal or visit developer.walmart.com to access your developer account.

3. If you don't have a developer account yet, click Sign up or Register and complete the registration process. You may need to provide information about your intended use of the Walmart API.

4. Once you have access to the Walmart Developer Portal, navigate to API Keys or My Applications to access your application management.

5. Create a new application or select an existing application from your dashboard. Click on the application name to open its settings.

6. In the application settings, navigate to the Credentials tab or API Keys section.

7. Under Client Credentials, you will find your Client ID and Client Secret. If these are not visible, click Generate or Create to generate new client credentials.

8. Copy both the Client ID and Client Secret immediately, as the Client Secret may not be accessible again after you navigate away from the page.

9. Store both credentials securely, as you will need them to configure your Nexla credential. The Client Secret is sensitive information and should be kept confidential.

The Client ID and Client Secret are used in Basic Authentication for all API requests to the Walmart API. The Client ID is used as the username and the Client Secret is used as the password. These credentials authenticate your requests and grant access to Walmart resources based on your account permissions. If your credentials are compromised, you should immediately revoke them in your Walmart Developer Portal and generate new ones. For detailed information about obtaining client credentials, API authentication, and available endpoints, refer to the Walmart API documentation.

Authenticate

Credentials required

As a Walmart customer, client ID and client Secret are needed to use Walmart Public API. You can refer to this link https://developer.walmart.com/doc/us/us-mp/us-mp-auth/

Field	Required	Secret	Description
Client ID	Yes	Yes	Walmart Client ID
Client Secret	Yes	Yes	Walmart Secret

Create a credential in Nexla

1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

New Credential Overlay – Walmart

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

3. Walmart uses Basic Authentication for all API requests. As a Walmart customer, Client ID and Client Secret are needed to use Walmart Public API. Enter your Client ID in the Client ID field. This is the Walmart Client ID you obtained from your Walmart Developer Portal (API Keys or My Applications). The Client ID is used as the username in Basic Authentication for all API requests to the Walmart API. The Client ID is sensitive information and must be kept confidential.

4. Enter your Client Secret in the Client Secret field. This is the Walmart Secret you obtained from your Walmart Developer Portal. The Client Secret is used as the password in Basic Authentication for all API requests to the Walmart API. The Client Secret is sensitive information and must be kept confidential.

   Your Walmart credentials (Client ID, Client Secret) can be found in the Walmart Developer Portal under API Keys or My Applications. As a Walmart customer, Client ID and Client Secret are needed to use Walmart Public API. The Client ID is used as the username and the Client Secret is used as the password in Basic Authentication.

   If your credentials are compromised, you should immediately revoke them in your Walmart Developer Portal and generate new ones. The credentials provide access to your Walmart account data and should be treated as sensitive information. Keep your credentials secure and do not share them publicly.

   For detailed information about obtaining client credentials, API authentication, and available endpoints, see the Walmart API documentation and Walmart API overview.

5. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Walmart connector tile, then select the credential that will be used to connect to the Walmart instance, and click Next; or, create a new Walmart credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Walmart endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

Get all orders

This endpoint template retrieves a list of all orders from your Walmart account. Use this template when you need to access order information, order details, or order metadata for analysis, reporting, or integration purposes.

• Enter the Created Start Date in the Created Start Date field. This should be the start date for filtering orders by creation date. The Created Start Date determines which orders will be retrieved. You can use Nexla macros like `{now}`, `{now - 70}` etc. The default value is `{now-70}` (70 days ago).
• Enter the Ship Node Type in the Ship Node Type field. This should be a list of Ship Node values that determines the fulfillment type for the orders. The Ship Node Type determines which orders will be retrieved. You can select from the available options: Seller Fulfilled (SellerFulfilled), WFS Fulfilled (WFSFulfilled), or 3PL Fulfilled (3PLFulfilled). The default value is SellerFulfilled.

This endpoint returns a list of all orders from your Walmart account, including order IDs, order details, shipping information, and other order metadata. The endpoint uses a two-step process: first, it obtains an access token using your credentials, then it retrieves orders using that token. The endpoint uses link header pagination to handle large result sets efficiently. Nexla will automatically follow the pagination to fetch subsequent pages of order data.

For detailed information about orders, API response structures, pagination, and available order data, see the Walmart API documentation.

Get all returns

This endpoint template retrieves a list of all returns from your Walmart account. Use this template when you need to access return information, return details, or return metadata for analysis, reporting, or integration purposes.

• This endpoint automatically retrieves a list of all returns from your Walmart account. No additional configuration is required beyond selecting this endpoint template. The endpoint uses a two-step process: first, it obtains an access token using your credentials, then it retrieves returns using that token.

This endpoint returns a list of all returns from your Walmart account, including return IDs, return details, refund information, and other return metadata. The endpoint uses a two-step process: first, it obtains an access token using your credentials, then it retrieves returns using that token. The endpoint uses link header pagination to handle large result sets efficiently. Nexla will automatically follow the pagination to fetch subsequent pages of return data.

For detailed information about returns, API response structures, pagination, and available return data, see the Walmart API documentation.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

Walmart data sources can also be manually configured to ingest data from any valid Walmart API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

Walmart API endpoints typically require a two-step authentication process: first obtaining an access token, then using that token to make API calls; manual configuration may require setting up chained API calls to handle this authentication flow. For the response data path, JSON responses commonly nest results under a structure like list.elements.order, so use a path such as $.list.elements.order[*] to extract individual order records; for XML responses, use an XPath such as /response/orders/order.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Walmart data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.