---
title: May 2026
slug: may-2026
docTags: 
createdAt: 2026-06-04T20:54:15.230Z
---

- **POST /v3/points-pools** - Added endpoint to create a new points pool. At least two initial active or invited members are required, and a member can belong to only one active pool at a time. 
- **DELETE /v3/points-pools/\{poolId}** - Added an endpoint to disband a points pool. 
- **GET /v3/points-pools** - Added an endpoint to search for points pools by `poolName`, `poolStatusCode`, or `memberIdentifier`. 
- **GET /v3/points-pools/\{poolId}** - Added endpoint to retrieve a points pool by ID. 
- **PUT /v3/points-pools/\{poolId}/members/\{memberIdentifier}** - Added endpoint to add a member to a points pool or update their membership status. Set `statusCode` to `Retired` to remove a member; if fewer than two active or invited members remain, the pool is automatically disbanded. 
- **GET /v3/redemption-items** - Added `poolRedeemable` boolean field to the `RedemptionItem` schema. Returns true if the member lacks sufficient currency for the item but belongs to a points pool with a sufficient combined balance. 
- **POST /v3/members/\{memberIdentifier}/redemptions** - Added `allowPoolRedeem` query parameter. When true and the member lacks sufficient currency, the shortfall is drawn from pool members' balances. 
- **PUT /v3/members/\{memberIdentifier}/redemptions/\{memberRedemptionId}** - Added `allowPoolRedeem` query parameter. When true and the member lacks sufficient currency, the shortfall is drawn from pool members' balances.
- **MemberRedemption schema** - Added `poolFunding` array field showing each contributing pool member and their points contribution when a redemption is funded by a points pool. For `validateOnly` requests, this is a preview; for saved redemptions, this is the final allocation. 
- **DELETE /v3/members/\{memberIdentifier}/redemptions/\{memberRedemptionId}** - Added `poolCancellations` array field to the response. When a pool-funded redemption is canceled, the field lists each contributing pool member whose child redemption was also canceled and the points returned to them. 
- **TransactionRelationship schema** - Added `POOL_REDEMPTION_CONTRIBUTION` and `POOL_REDEMPTION_SOURCE` relationship types. `POOL_REDEMPTION_CONTRIBUTION` identifies a pool member's points contribution toward a pool redemption; `POOL_REDEMPTION_SOURCE` identifies the redemption that triggered the contribution. 
- **PUT /v3/redemption-rules/\{code}** - Added endpoint to fully replace an unreleased redemption rule. All fields are overwritten with the values provided. Only rules in `WORKING` or `READY` status may be replaced. 
- **PATCH /v3/redemption-rules/\{code}** - Updated to use a dedicated `RedemptionRulePatchRequest` schema supporting partial updates. Only fields included in the request body are modified; absent fields remain unchanged. The following fields can be explicitly set to null to clear their value: `endDate`, `faceValue`, `minimumRoleRequired`, `rank`, `rawExpression`, `externalCode`. 
- **POST /v3/members/\{memberIdentifier}/earnings** - Added `useCouponCodes` array field to the earn transaction request. Accepts a list of unique coupon codes for which a coupon use is posted upon processing. Only coupons in `Held` status are accepted. 
- **BonusRule schema** - Added `rewards` array field returning a list of `RuleReward` objects, each describing a reward associated with the bonus rule, including `rewardType`, `rewardResultType`, `description`, `code`, and `amount`. 
- **PATCH /v3/members/\{memberIdentifier}** - Reduced the maximum length of the `middleName` field from 100 to 50 characters in `MemberPatchRequest`.