Getting Started

The following are getting started procedures for making GoLocal requests.

Step 1
Use the following header values for most requests. Contact a Walmart Client Center's Walmart administrator, client administrator, or development management for these values.

Value	Meaning
`WM_CONSUMER.ID` or `client_id`	This is the Client Consumer ID of the authentication process.
`client_secret`	This is the client secret of the authentication process. Not all requests require the client_secret. When it is used, it is important to keep this value secured.

Step 2
Select a Walmart GoLocal account type. These are either:

Account Type	Use Case	Base URL
Production account	The production account is live for the client and so uses actual information and may be a deployed application. Because the information is proprietary, access could be limited. Contact your system administrator for details.	`https://developer.api.us.walmart.com/api-proxy/service/supplychain/transportation/v1/daas`
Sandbox account	The sandbox account may be used during development or for testing. The information is isolated from production accounts and so does not risk corrupting production data.	`https://developer.api.us.walmart.com/api-proxy/service/supplychain/transportation/v1/sbx-daas`

Step 3
Generate an access token for each request made.

To create the access token, see the Create an authentication token request (POST https://developer.api.us.walmart.com/api-proxy/service/identity/oauth/v1/token).

For more information about authentication and authorization details, contact a Walmart GoLocal Account Manager at: [email protected].

Step 4
Make individual requests. See the Walmart GoLocal Reference section for details of each request.