The Walmart Marketplace APIs use OAuth for token-based authentication and authorization. This is the new standard method which should be used moving forward. The benefits of using of token-based authentication include:
- Current standards for API Authentication
- Reduced overhead of creating and signing the digital signature
- Easier integration with Walmart APIs
- Reduced number of headers per API call
- Log into the portal to create your API key. Click My Account and select login type, either Marketplace or DSV.
- Create your Client ID and Client Secret from the API keys page.
- Generate a temporary token (expires in 15 minutes) for your software. Call the Token API and specify your Client ID and Client Secret.
- Use the headers listed in the table below to authenticate your API call. These headers are mandatory for all API calls for authentication. Individual APIs may require additional headers.
Note: You must contact your Solution Providers to provide the Client ID/Client Secret.
Common Header Parameters
The common headers are required and shared among all of the APIs. These headers are included to implement standards across APIs and provide the function of tracking and debugging issues.
|WM_SVC.NAME||Walmart Service Name||Yes||Walmart Marketplace|
|WM_QOS.CORRELATION_ID||A unique ID which identifies each API call and used to track and debug issues; use a random generated GUID for this ID||Yes||1234hfvgtr|
|WM_CONSUMER.CHANNEL.TYPE||A unique ID to track the consumer request by channel||No||0f3e4dd4-0514-4346-b39d-… use the Consumer Channel Type received during onboarding|
|Authorization||Basic authorization header. Base 64 encodes the Client ID and Client Secret retrieved in step two of the integration steps.||Yes||Basic YzcyOTFjNmItNzI5MC00….|
|WM_SEC.ACCESS_TOKEN||The token retrieved in step three of integration||Yes||eyJraWQiOiIzZjVhYTFmNS1hYWE5LTQzM…..|