July 2026
0 min
- POST /v3/communication-types - Added endpoint to create a communication type.
- PUT /v3/communication-types/{communicationCode} - Added endpoint to update a communication type (the channel cannot be changed after the communication type is created).
- GET /v3/communication-types - Added endpoint to find communication types, with filtering by name, channel, or statusCode.
- GET /v3/communication-types/{communicationCode} - Added endpoint to retrieve a communication type by its code.
- GET /v3/rewards/redemption-rules - Added findRedemptionRewards endpoint, returning a smaller, catalog-safe response (no rule expressions) for displaying redemption options to a member. Replaces the now-deprecated GET /v3/redemption-items.
- GET /v3/redemption-items - Deprecated in favor of GET /v3/rewards/redemption-rules.
- RedemptionReward schema - Restructured: redeemable, poolRedeemable, redeemText, and requirePartnerAccountNumber moved into a new nested RedemptionRewardContext object (rewardContext). Added requireAddress field indicating whether an address is required at redemption time (collected via orderAddress).
- GET /v3/redemption-rules - Removed the memberIdentifier query parameter. Use GET /v3/rewards/redemption-rules for member-filtered results.
- RedemptionRule schema - Added dataReleaseName and dataReleaseItemStatus fields, so callers no longer need a separate lookup to identify which data release a rule belongs to.
- GET /v3/redemption-rules - Removed the 500-record cap; the endpoint now returns all matching records with no upper limit, intentionally unbounded to support client-side filtering.
- PATCH /v3/members/{memberIdentifier}/transactions/{transactionId} - Added subReasonCode field to the transactionAdjustment object.
- PATCH /v3/members/{memberIdentifier}/transactions/{transactionId} - Added validateOnly query parameter. When true, the edit is validated but not saved, and the response returns the resulting point/revenue delta (EditMemberTransactionResponse) so a confirmation screen can show the impact before submitting.
- PATCH /v3/members/{memberIdentifier} - Added scrub query parameter. When true, all PII is removed from the member record; non-PII fields included in the request body (such as closedReasonCode) are still applied. Requires the api:member:scrub scope in addition to api:member:modify.
- GET /v3/members/comments - Added title query parameter for filtering comments across all members by title.
- MemberTransactionRedemption schema - Added poolName field so pool-related redemptions can show which points pool they belong to in transaction history.
- Coupon schema - Added couponRequestId field, identifying the coupon request that generated the coupon.
- UserTask schema - Added locked, lockerId, lockerName, and lockerRank fields, so the current My Tasks UI can show lock status the same way the legacy UI does.
- MemberEnrollRequest and MemberEnrollResponse schemas - Added an additionalProperties object to support passing partner-specific identifiers through member enrollment.
- transferPoints and createReferralCode endpoints - Added 403 Forbidden response declarations.
- POST /v3/users - Added full set of error response declarations (400, 401, 403, 404, 409, 500).
- GET /v3/data-releases - Added format: date to the publishStartDate and publishEndDate query parameters.
- customData swagger tag - Renamed to custom-data for kebab-case consistency across API endpoints.
- MemberRedemption and MemberTransaction schemas - Fixed field types: memberRedemptionId corrected from object to integer; memberIdentifier on one schema corrected from integer to string.
- MemberLinkedAccountResponse schema - Updated formatting on startDateTime, endDateTime, and updateDateTime with the standard format: date-time annotation.
- Datacode-referenced field descriptions - Rewrote descriptions for fields whose values depend on client-configured datacodes (ace01–ace15, accountStatusCode, accountTypeCode, genderCode, enrollmentSourceCode, enrollmentDeviceTypeCode, closedReasonCode, and address/email/phone type and status codes). No field, type, or behavior change.
- Member comments endpoints - Retitled to "Get/Create Member Comments / Call Logs" and updated the reason/subReason field descriptions to reference their datacode CodeTypes (CommentReason, CallLogSubReason) instead of a hardcoded value list. No field, type, or behavior change.