July 2026

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