Skip to content

Walmart Marketplace · seller alert

Walmart Delegated Access Keys Are Expiring: What Stops Working in September 2026 (and How to Fix It)

If you run a Walmart Marketplace store and use any third-party tool — a repricer, a listing tool, an inventory or order sync — there's a decent chance it talks to Walmart using something called a “Delegated Access” key. Walmart is retiring that method. If your provider hasn't already migrated you, your tool will stop pulling and pushing data at some point this fall.

This post is just the facts: what changed, how to check if you're affected, and what to do about it. I run a Walmart store with 2,000+ SKUs and I'm also building a repricer, so I'm going through this same App Store re-approval process myself — that's the extent of any pitch here.

What actually changed (with dates)

Per Walmart's developer documentation (Delegated Access Authorization):

  • The ability for approved Solution Providers to create new Delegated Access keys was retired on July 30, 2026. If your provider hadn't switched you to OAuth 2.0 before that date, they can no longer generate a fresh delegated key for your account.
  • Existing Delegated Access keys will keep working until the end of September 2026. After that, per the same docs, all Delegated Access keys stop functioning, and the Delegated Keys section is being removed from the Developer Portal entirely.

I could confirm those two dates on Walmart's current developer docs page, but not on a second, independent source. The “API Newsletter” page I checked (marketplace.walmart.com/?p=9031) turned out to be an older notice, dated August 2022, about the “My API Key” system — not a fresh announcement of this retirement. So the dates above are sourced to the developer docs page specifically; check it yourself, since Walmart has moved deadlines before. [UNVERIFIED]: no Walmart source I found gives the exact day in September, only “end of September 2026.”

Separately, Walmart's Seller Center guide on connecting a solution provider (Marketplace Learn) confirms OAuth 2.0 authorization for connected apps requires annual renewal — this isn't a one-time fix.

Who's affected — check in two minutes

Log into Seller Center → Apps → App Listings, then check Connected Apps (under the App Store heading). If a tool you rely on is there and was connected using an older delegated-key flow rather than a fresh OAuth authorization, it's in scope.

Practical test: did you (or your provider, on your behalf) ever generate a “Delegated Access key” for that integration — versus going through an OAuth “Authorize” screen in Seller Center? If unsure, ask your provider directly. A provider that's already migrated will typically have already asked you to click “Connect” and “Authorize” again in recent months.

What breaks, and when

  • Before July 30, 2026: providers could still issue new delegated keys for unmigrated accounts. That window is closed.
  • Now through end of September 2026: existing delegated keys keep working — your grace period.
  • After end of September 2026 (per Walmart's docs): the key stops authenticating. Depending on how your tool is built, that typically means price updates stop pushing, inventory syncs stop pulling, order data goes stale, or the tool throws auth errors. Your listings aren't deleted — the connection between your tool and Walmart's API breaks.

The fix — 4 steps

  1. Reauthorize through the App Store Connect button. In Seller Center: Apps → App Listings → find your provider's app → Connect → review the authorization screen → agree to the privacy policy → Authorize. This is Walmart's documented flow for connecting an approved Solution Provider.
  2. Confirm with your provider that this completes the migration. Some need you to reauthorize on their end too after the Walmart-side click. Ask — don't assume.
  3. If your provider isn't in the Walmart App Store at all, that's bigger than a key expiring — it likely means they were never approved, or their listing lapsed. Ask how they'll keep the integration running past September 2026; no clear answer means start evaluating alternatives now, not in October.
  4. Calendar the annual renewal. OAuth authorization needs yearly renewal (“renew” under Connected Apps) — this migration isn't the last time you'll touch this.

What if you use your OWN keys, not a provider's?

If you built your own script and generate your own API credentials directly — Walmart calls this “My API Key,” issuing a Client ID and Client Secret — you are not using Delegated Access, and this retirement does not apply to you. Delegated Access exists for when a third-party Solution Provider calls Walmart's API on your behalf, with a key generated by their integration. Walmart's own guidance states sellers “should not use delegated access API keys” for their own direct usage — that path has always been “My API Key.”

Quick test: if a company other than you had to be “approved” by Walmart to get your key working, it's probably delegated. If you generated Client ID/Secret yourself in Seller Center, it's not.

Checklist

  • Seller Center → Apps → App Listings → Connected Apps
  • List every third-party tool connected to your account
  • Ask each provider: Delegated Access, or already OAuth 2.0?
  • Connect → Authorize for anything still on the old method
  • Confirm reauthorization is complete on the provider's side too
  • No App Store listing or no migration plan → evaluate alternatives now
  • Set a recurring reminder to renew OAuth annually
  • Test now, while you still have a working fallback

Sources

I run a Walmart store with 2,000+ SKUs and we're building a repricer at Lumi — going through this same App Store approval process ourselves, which is why I dug into the actual dates instead of relying on a provider's email.

Already checking your Walmart Buy Box while you're in Seller Center?

If you're pulling reports while you sort out reauthorization, the free Buy Box report analyzer reads your downloaded report in your browser — no upload, no signup, no store connection.

Analyze your Buy Box report free →