Walmart Authentication
Walmart Marketplace APIs authenticate with OAuth 2.0 client credentials. A seller (or an approved Solution Provider acting for a seller) exchanges a Client ID / Client Secret for a short-lived access token at POST /v3/token — the token request itself is HTTP Basic (base64 clientId:clientSecret in Authorization). Every subsequent call carries the token in the WM_SEC.ACCESS_TOKEN header alongside three required Walmart service headers. This replaced an older signature scheme (WM_CONSUMER.ID + WM_SEC.TIMESTAMP + WM_SEC.AUTH_SIGNATURE from a Consumer ID / Private Key pair), which is retired. Authorization granularity is per object category (Items, Orders, ...) assigned to the credential, not OAuth scopes: seller credentials carry full access, Solution Provider credentials start with none. Delegated Access keys are being retired — new issuance stopped 2026-07-30 and existing keys stop working at the end of September 2026, replaced by OAuth 2.0 seller authorization through the Walmart App Store.
Walmart secures its APIs with oauth2 and http across 2 declared security schemes, as derived from its OpenAPI definitions.
Security Schemes
Source
Authentication Profile
Work with this as data
Every security artifact here is available over the APIs.io API and to AI agents over MCP.