Walmart Affiliate Marketing API

# Fix list: Walmart Affiliate Marketing API

From Anchor Terminal's listing at https://www.anchorterminal.com/tools/walmart-affiliate-api, the October 2026 research run, assessed 14 October 2026. Grade E, 38.6 out of 100.

This is everything the published grade says the listing lacks, the biggest possible gain to the total first. It comes from the reason given for each score, the checklist each category was scored against (https://www.anchorterminal.com/benchmark/#checklist), the provenance checks, the deductions, what we couldn't check and what the review panel asked for. A fix counts at the next check, once it's public.

For a coding agent working on Walmart Affiliate Marketing API: work through the items below in the product, its docs and its public pages. Each category gives the reason for its score, with the points each checklist item earned, and the checklist itself, so the gap is the items that earned less than their points. Change the product, not the wording, and keep a note of what you changed and where it's published.

## 1. Reliability, 33 out of 100, up to 13.4 more on the total

Why it scored 33: No status page was found. status.walmart.io did not answer and the portal links none (0 of 20). No readable incident history, so the 5-point default (5 of 30). The API terms state 5,000 calls a day (15 of 15). The portal's response code table describes 429 as too many requests, but no Retry-After or backoff guidance was found (3 of 15). No SLA (0 of 10). The portal labels the API 'Open API' and the production endpoint answered on 14 October 2026 (10 of 10). Total 33.

The checklist (https://www.anchorterminal.com/benchmark/#checklist-reliability):

Hosted APIs, MCP servers, models and platforms.

- 20, a public status page with component history (Statuspage, Instatus, BetterStack or the vendor's own).
- 0 to 30, the incident record for the last 90 days on that page. 30 for a clean record or trivial incidents only, 20 for minor incidents only, 10 for one major outage (an hour or more of a core API down, or errors across the board), 0 for several. 5 when there's no history we could read, and the note says so.
- 15, rate limits documented with numbers.
- 15, documented 429 or overload handling (Retry-After, backoff guidance), and idempotency keys or safe-retry guidance where writes are involved.
- 10, an SLA published for any paid tier.
- 10, the surface agents use is generally available, not beta or preview.

Local packages, SDKs, frameworks and stdio MCP servers.

- 20, installs from an official package with supported runtimes stated.
- 25, a public CI and test suite, passing on the default branch.
- 0 to 25, open crash or regression issues relative to activity (25 for few and handled, 0 for many, old and unanswered).
- 15, semver discipline and breaking changes called out in a changelog.
- 15, version 1.0 or later, or declared stable.

Protocols are read from their reference implementations, the public facilitators or servers, spec stability and test vectors.

## 2. Schema & documentation, 27 out of 100, up to 11.9 more on the total

Why it scored 27: No OpenAPI or machine-readable description for the affiliate API. Its specification page is marked as not a Swagger document (0 of 25). No llms.txt or Markdown, and pages render only through browser script (0 of 10). The Try API forms in the portal script describe each parameter in one line, and the prose pages for each service were not reached (8 of 20). Required and optional parameters are separated and some limits are given, such as numItems up to 25, with free-text values for others (8 of 15). Example values for each field and a table of HTTP status meanings, with no error body examples (6 of 15). The version is in the path (v2) and the live service reports version 2.0.0, with no changelog found (5 of 15). Total 27.

The checklist (https://www.anchorterminal.com/benchmark/#checklist-schema):

APIs and MCP servers.

- 25, a machine-readable contract (a public OpenAPI file or similar; for MCP, typed JSON Schema inputs on every tool).
- 10, llms.txt or Markdown docs served for agents.
- 0 to 20, descriptions that say what a tool is for, when to use it and when not to, read from the tool definitions in the source or the API reference.
- 0 to 15, typed inputs with enums, constraints and required fields, and no free-form JSON blobs.
- 0 to 15, examples and documented error responses.
- 15, versioning and a public changelog.

Models are read from the API reference, the OpenAPI file, llms.txt, the structured-output and tool-use docs and the model cards. Frameworks from docs a model can follow, typed interfaces, examples and the API reference.

## 3. Payments & pricing, 25 out of 100, up to 9.4 more on the total

Why it scored 25: No x402, MPP or L402 (0 of 40). No fee for calls is stated. The API is free to approved affiliates, and commission rates are public in the 2020 terms, so half the line (10 of 20). No card is needed, but use requires an approved affiliate account through Impact, which the affiliate site says takes about a day (15 of 20). Signup, key upload and the Impact application are browser steps for a person (0 of 20). Total 25.

The checklist (https://www.anchorterminal.com/benchmark/#checklist-payments):

The published rubric, also on the [x402 page](https://www.anchorterminal.com/x402/).

- 40, a machine payment protocol (x402, MPP or L402) on the tool's own endpoints. 10 to 30 when it covers only some endpoints or only goes through a third party, and the note says which.
- 20, per-call or per-unit pricing published without a login. 10 for public plan-only pricing, 0 for "contact sales" or prices behind a login.
- 20, a free tier or trial that doesn't need a card.
- 20, autonomous onboarding, meaning an agent can get access without a person signing up in a browser (keyless use, x402, a programmatic key API).

Payment platforms and agent wallets rarely charge for their own API over a machine protocol, so the first line has steps for them, and the highest one that applies counts. 40 when x402, MPP or L402 runs on all their own endpoints, 30 when it runs on part of their own API, 25 when their merchants can accept one, 20 for running a facilitator, 15 for paying as a buyer, and 0 when the only protocol is their own. Merchant acceptance sits above a facilitator because the platform's own customers can charge agents through it, while a facilitator settles for sellers who wire up the protocol themselves. The counter-argument (a facilitator does more for the protocol as a whole) has a point. Each note says which step applied.

Open-source software you run yourself is scored on its hosted or paid option if it has one. A free, self-hosted package with nothing to buy gets 20, 20 and 20 for the last three lines, and 0 to 40 for the first only if it ships a payment protocol.

## 4. Maintenance & community, 5 out of 100, up to 8.3 more on the total

Why it scored 5: No dated release, changelog or change notice for the affiliate API was found (0 of 30). No dated entries in the last 90 days (0 of 20). Support is through a support form and a Gitter room named IO-support/community in the portal code, and replies were not tested (5 of 15). No official SDK (0 of 15). No public package, repository or CI (0 of 10). Total 5.

The checklist (https://www.anchorterminal.com/benchmark/#checklist-maintenance):

- 0 to 30, time since the last release, or the last published model or API change for a closed service. 30 within 30 days, 20 within 90, 10 within 180, 0 older.
- 20, at least three releases or dated changelog entries in the last 90 days.
- 0 to 25, responsiveness. Issues and pull requests answered on GitHub (the open issues and how recent the replies are). For closed services, a public changelog and a support or community channel that answers, 0 to 15.
- 15, presence in the official MCP registry under a verified namespace (MCP servers), or current official SDKs (APIs and models).
- 10, package health, current dependencies and CI.

Models are read for deprecation notice periods and model churn rather than release counts.

## 5. Security & auth, 58 out of 100, up to 7.4 more on the total

Why it scored 58: Requests are signed with the developer's RSA private key, which is never sent, and signatures expire after 180 seconds. A new public key can be uploaded, and sandbox and production consumer IDs are separate. There are no scopes beyond the subscribed product (22 of 30). The affiliate API only reads, so it cannot buy or change an account. Checkout sits behind a separate approval (15 of 20). Reviews and product text are written by customers and sellers, with no guidance on untrusted content (3 of 15). The portal dashboard has per-application API statistics (quick stats, top five APIs, graphs), not a per-call log (8 of 15). www.walmart.com/.well-known/security.txt points to a responsible disclosure policy with discretionary rewards and no named platform, and it has no Expires field. No certification was checked (10 of 20). Total 58.

The checklist (https://www.anchorterminal.com/benchmark/#checklist-security):

- 0 to 30, the credential model. 30 for OAuth 2.1 with scopes, or scoped and revocable keys with rotation. 20 for plain revocable API keys. 10 for one all-powerful key. 10 off when a secret can travel in a URL query string as a documented option.
- 0 to 20, read-only or least-privilege modes, and confirmation or approval for destructive actions.
- 0 to 15, prompt-injection posture where the tool returns untrusted content (documented mitigations or guidance). A tool that returns no untrusted content gets 10.
- 0 to 15, audit logs or per-call visibility for the operator.
- 0 to 20, a security programme. security.txt or a disclosure policy, a bug bounty, SOC 2 or ISO 27001, advisories handled in public.

Models are read for retention, whether API data trains models (and whether that's off by default), zero-retention options and certifications. Frameworks for telemetry defaults, approval hooks, guardrails and sandboxing.

## 6. Agent ergonomics, 57 out of 100, up to 7 more on the total

Why it scored 57: responseGroup base or full and numItems up to 25 size responses, without field selection (15 of 25). Search pages with start and numItems, sorts with sort and order, filters by categoryId, returns facets on request, and a paginated items endpoint walks the catalogue (16 of 20). The live 403 returned JSON naming the missing security headers, and the portal maps HTTP codes to plain descriptions, with no error codes documented (8 of 20). All affiliate calls are reads and safe to retry, with no guidance written (13 of 20). Only query is required for search. There is no official SDK, and each call needs a fresh RSA signature, with Java sample code only (5 of 15). Total 57.

The checklist (https://www.anchorterminal.com/benchmark/#checklist-ergonomics):

- 0 to 25, context cost. For MCP, the number and size of the tool definitions (25 for ten or fewer compact tools, 15 for 11 to 30, 5 for more than 30, plus up to 10 back for toolsets, dynamic loading or read-only subsets). For APIs, whether responses can be sized (field selection, limits, summaries).
- 20, pagination, filtering and output-size controls.
- 20, actionable, documented error responses, codes and messages an agent can recover from.
- 20, idempotency or safe retries, and for MCP the `readOnlyHint` and `destructiveHint` annotations.
- 15, sensible defaults, few required parameters, and official SDKs in at least two languages.

Models are read for tool use, structured output, prompt caching, context length, batch and SDKs. Frameworks for how much code and how many defaults a tool-calling agent with MCP needs.

## 7. Transparency & trust, 53 out of 100, up to 4.1 more on the total

Made of editorial 34, provenance 71.

Why it scored 53: Closed service with API terms shown in the portal, last updated 30 September 2020. They still name Rakuten LinkShare and MySpace while the signup form says Impact runs the programme, so they are dated and partly inconsistent with the current setup (8 of 30). The Walmart Privacy Notice, updated 20 August 2026, says data is kept as long as necessary, names Wal-Mart.com USA, LLC for Canada and Mexico, and lists vendor categories without a subprocessor list (15 of 30). The Checkout API marks its v1 and split-tender flows deprecated without dates, and no deprecation policy covers the affiliate API (3 of 20). Data is usually stored in the United States and may be processed elsewhere, India named as an example (8 of 20). Total 34.

The checklist (https://www.anchorterminal.com/benchmark/#checklist-transparency):

- 0 to 30, source availability and licence clarity. 30 for open source under an OSI licence, 15 for closed with clear terms, 0 for unclear terms.
- 0 to 30, data handling and retention statements that agree with each other (privacy policy, DPA, retention periods, subprocessors).
- 0 to 20, a deprecation policy or notices with dates.
- 0 to 20, telemetry disclosed with an opt-out (local software), or subprocessors and data locations disclosed (hosted).

The other half of Transparency and trust is the provenance score, computed from checked facts (below). The category score is the mean of the two.

Provenance checks not met in full (half of this category, computed from checked facts):

- Terms of service: read, states 6 of the 7 things a reader expects, and has 3 clauses that cost points (3.1 of 10)
- Privacy policy: read, states 8 of the 8 things a reader expects, and has 1 clause that costs points (8 of 10)
- Status page: not found (0 of 10)
- Changelog: not found (0 of 10)

## What we couldn't check

What we couldn't read counted as absent. Publishing it on a page a plain HTTP fetch can read (not only in a browser) lets the next check count it.

- unchecked: the walmart.com Terms of Use, which answered with a bot check, including any clause on robots or automated purchases.
- unchecked: the walmart.io prose pages for the introduction, quick start, additional headers, each service, item response groups and the affiliate specification. They load through browser script, and only the portal script was read.
- unchecked: whether the Walmart I/O API terms dated 30 September 2020 are the current version. They name Rakuten LinkShare while the signup form names Impact.
- unchecked: Checkout API access terms and who qualifies. The portal says it needs additional approval and a sound business case.
- No official Walmart MCP server or public agent checkout programme was found. Walmart's appearance inside other assistants is not an interface an outside agent can call.

## Weaknesses

- No order, cart, order status or return operation in the affiliate API
- The documentation is rendered by browser script, with no OpenAPI, llms.txt or Markdown
- The API terms were last updated on 30 September 2020 and name Rakuten LinkShare, not Impact
- No status page, changelog or official SDK was found
- The walmart.com Terms of Use answered with a bot check, so rules for automated buyers on the store were not read

## What costs an agent a turn today

The notes we give agents before they call it. Each one is a workaround an agent shouldn't need.

- Generate a fresh WM_SEC.AUTH_SIGNATURE for each call, because a signature older than 180 seconds is rejected
- Keep below 5,000 calls a day per application
- Pass the Impact publisher ID so returned links earn commission
- Hand purchases to the person through the returned product link, since the affiliate API cannot check out

## When it's done

Send what changed and where it's published as a dispute (https://www.anchorterminal.com/builders/#disputes, or `POST https://www.anchorterminal.com/api/v1/contact` with `"kind": "dispute"`). Disputes are answered in public, and the listing is checked again by the same checklist. Paying for an audit or a listing claim changes nothing here.