---
title: April 2026
slug: april-2026
docTags: 
createdAt: 2026-04-21T13:46:16.067Z
---

- **POST /v3/members/\{accountNumber}/transfer** - Added `transactionId` field to the `PointsTransferResponse` schema; the value matches the `transactionId` of the resulting bonus accrual. 
- **PATCH /v3/members/\{memberIdentifier}** - New endpoint for partial member profile updates; the API applies only the fields in the request body, and fields set to null clear the corresponding value. Supports updates to member profile fields, including `firstName`, `birthDate`, `accountStatusCode`, `closedReasonCode`, `companyName`, `testAccount`, and ASCII name variants. 
- **POST /v3/members/\{memberIdentifier}/redemptions** - Added `externalCode` field to the redemption request body; when provided, the system identifies the highest-ranked redemption rule the member qualifies for within that external code grouping. Do not provide `redemptionItemCode` or `offerCriteria` when using `externalCode`.
- **GET /v3/data-releases** - New endpoint used to search data releases by status, text, and publish date range. Supports optional query parameters `text`, `statusCode`, `publishStartDate`, `publishEndDate`, `includeItemSummary`, `includeItems`, and `includeStatusHistories`. Requires the `api:data-release:read` scope.
- **GET /v3/event-rules** - Renamed the `workflowStatus` query parameter to `dataReleaseItemStatus`; accepted values are `WORKING`, `READY`, `APPROVED`, `PUBLISHED`, `LIVE`, `ENDED`, and `CANCELED`. 
- **GET /v3/members/\{memberIdentifier}/comments** - Fixed field casing: `memberidentifier` now returns as `memberIdentifier` in the `MemberComment` schema.
- **POST /v3/members** - Added optional `closedReasonCode` field to the `MemberEnrollRequest` schema; enrollment with `accountStatusCode: C` and `migrate: true` requires a valid `closedReasonCode`. Accepted values: `deceased`, `member`, `merge`, `other`, `fraud`. 
- **GET /v3/probonuses** - New endpoint to search promotions and bonus rules by code. Supports optional `code` and `type` query parameters (`PR` for promotions, `BR` for bonus rules). Returns a `ProBonusSearchResult` with a count, promotions list, and `bonusRules` list. Requires the `api:promotion:read` scope.
- **GET /v3/members/\{memberIdentifier}/transactions/referenceId;\{referenceId}** - Added `includeAdjustments` query parameter to lookup provided `referenceId` against `EXTERNALSTATEMENTID` of Accrual table; when true, adjustment transactions appear in the response.
- **GET /v3/audit/\{tableName}** - Added `entityKey` field to the `AuditLogEntry` schema; returns the external identifier for the audited entity when available (for example, a tier code or location code).
- **POST /v3/redemption-rules** - Added `externalCode` field to the `RedemptionRule` schema for grouping rules under a shared external identifier. 
- **GET /v3/redemption-items** - Deprecated in favor of using the `/redemption-rules` endpoints instead. 
- **GET, PUT, PATCH, DELETE /v3/event-rules/\{eventRuleCode}** - Event rule single-resource endpoints now accept `eventRuleCode` (string) as the path parameter instead of `eventRuleId` (integer).
- **PATCH /v3/redemption-rules/\{code}** - Changed from `PUT /v3/redemption-rules/{id}` (integer path parameter) to `PATCH /v3/redemption-rules/{code}` (string). Added `merchant` field for partner-based fulfillment and a read-only `id` field to the `RedemptionRule` schema. 
- **GET /v3/event-rules** - The `EventType` schema now includes a `contextFields` array listing the Event Context expression field names populated by `TYPED_CONTEXT` event types. The `EventTypeEligibility` schema now includes a context flag indicating whether event context eligibility applies to the event type.  
- **GET /v3/members/\{memberIdentifier}/tiers** - Added `sourceCouponUse` field to the tier history response for tiers awarded through a tier gift; the field includes `couponCode`, `offerCode`, `offerName`, `startDate`, and `endDate`. 
- **POST /v3/call-logs/\{memberCommentId}/locks** and **DELETE /v3/call-logs/\{memberCommentId}/locks** - New endpoints to lock and unlock call log entries. Requires the `api:member-comments:modify` scope. 
- **POST /v3/members/\{memberIdentifier}/transactions/\{transactionId}/clone/\{targetMemberIdentifier}** - Added `maxLength: 4000` validation to the `comment` field in the `CloneMemberTransactionComment` schema.
- **GET /v3/outbound-notifications/\{type}** - Corrected the documented `pageSize` maximum from 10000 to 500, reflecting actual enforced behavior.