# May 2026 Release Notes

<HTMLBlock>{`
<h1><span style="color: #4DBDF5;">Launch</span></h2>
`}</HTMLBlock>

## PATCH API Enhancements for Campaign Management

**Availability:&#x20;**&#x53;andbox and Production

PATCH support is now available across Display Campaign Management APIs, enabling **partial updates** to campaigns and related entities.

Previously, updates required full object replacement via PUT, increasing payload size and risk of unintended overwrites. PATCH allows you to update only the fields that have changed

### **Endpoints**

* [PATCH /api/v1/campaigns](https://developer.walmart.com/advertising-partners/docs/update-campaign-patch)
* [PATCH /api/v1/adGroups](https://developer.walmart.com/advertising-partners/docs/update-existing-ad-group-patch)

### **Key capabilities**

* **Partial updates:** Only provided fields are updated; omitted fields remain unchanged
* **Batch support:** Multiple entities can be updated per request
* **Field-level control:** Supports granular updates across budgets, bids, and targeting.
* **Consistent validation:** Existing business rules from PUT APIs remain enforced

### **Recommended usage**

Use PATCH for:&#x20;

* Bid and budget adjustments
* Targeting updates

Continue using PUT for:&#x20;

* Full object replacements

### **Backward compatibility**

* No breaking changes
* Existing PUT endpoints remain supported

<br />

<HTMLBlock>{`
<h1><span style="color: #4DBDF5;">Enhancement</span></h2>
`}</HTMLBlock>

## Near real-time performance API enhancements for budget and pacing visibility

**Availability:&#x20;**&#x53;andbox and Production

Walmart Connect has enhanced the near real-time performance API to provide additional pacing, budget, and out-of-budget visibility for campaigns and ad groups.

These updates are designed to support more informed optimization decisions and provide greater operational visibility through API integrations.

### **Endpoint**

[GET /api/v1/stats](https://developer.walmart.com/advertising-partners/docs/real-time-delivery-performance-api)

### **New capabilities**

**Metrics enhancements: &#x20;**&#x54;he metrics object now includes `validBids`

### New budget object

Budget details are now returned for supported entities

**Budget fields**

| Field                  | Description                                                           |
| ---------------------- | --------------------------------------------------------------------- |
| `sourceLevel`          | Indicates whether budget is managed at `CAMPAIGN` or `AD_GROUP` level |
| `type`                 | `DAILY` or `TOTAL`                                                    |
| `daily.limit `         | Configured daily budget                                               |
| `daily.remaining `     | Remaining daily budget                                                |
| `daily.outOfBudgetAt ` | Timestamp when budget exhausted                                       |
| `total.limit `         | Configured total budget                                               |
| `total.remaining `     | Remaining total budget                                                |
| `total.outOfBudgetAt ` | Timestamp when budget exhausted                                       |

### New Pacing Object

Pacing visibility is now available within API responses.

**Pacing fields**

| Field            | Description                    |
| ---------------- | ------------------------------ |
| `sourceLevel`    | Indicates pacing source level  |
| `pacingPercent`  | Percentage pacing progress     |

### Additional behavior updates

* Near real-time performance API data continues to refresh near real time (≤15 minutes)
* `timeWindow` applies only to metrics objects
* Budget and pacing objects are returned consistently for supported entities

### Backward compatibility

* Existing Near real-time performance API integrations remain supported
* All new fields are additive only
* No existing response fields have been removed or renamed

<br />

<HTMLBlock>{`
<h1><span style="color: #4DBDF5;">Update</span></h2>
`}</HTMLBlock>

## Moderation Assist (beta)\*

To align with the updated Walmart Connect Advertising Policies, we are making corresponding updates to the Moderation Assist API (beta).

As part of this transition, the `prohibited_Contents` response within the Moderation Assist API results endpoint will be temporarily paused while we implement, retrain, and validate models against the updated policy requirements. During this period, `prohibited_Contents` will return an empty array, but the following response fields will remain available for use:

* `acknowledgementClaims`
* `substantiationClaims`
* `altText`

### Learn More

Read the [Walmart Connect Ad Policy](https://advertisinghelp.walmart.com/s/guides?channel=Display\&language=en_US\&article=000009813) guide.

***

## Overview of API Changes

| Endpoint                                                                                                               | Change Type | Summary of Change                                                                    |
| ---------------------------------------------------------------------------------------------------------------------- | ----------- | ------------------------------------------------------------------------------------ |
| [Get Moderation Assist results](https://developer.walmart.com/advertising-partners/docs/GET-Moderation-Assist-Results) | Launch      | `prohibited_Contents` response will be temporarily paused and return an empty array. |

\*This beta is subject to [Walmart Connect Product Terms for Beta/Innovation Products](https://advertisinghelp.walmart.com/s/guides?channel=Display\&article=000010103).&#x20;