Release Notes - 06-January-2025
The 06-January-2025 release introduces potentially breaking changes to the Triple API. The changes are detailes below.
Breaking
All decimal numbers are now returned as strings that can be parsed into decimals. These values can still be sent to Triple as decimals, but doing so is deprecated. The impacted fields include:
latitude
longitude
transaction_amount
reward_amount
loyalty_conversion_rate
distance
estimated_allocation
offer_marketing_rate
offer_marketing_value
maximum_reward_per_transaction
offer_minimum_spend
offer_reward_rate
offer_reward_value
revenue_share
Non-Breaking
Rather than being described as a number, all total fields are now integers. This is a non-breaking change, as the value of total will not be affected. Impacted endpoints:
GET /partner/card-accounts
GET /partner/card-programs
POST /partner/card-accounts/{card_acount_id}/offers.recommendations
POST /partner/card-accounts/{card_acount_id}/offers.search
GET /partner/merchants.search
GET /partner/offer-filters
GET /partner/card-exclusions
GET /partner/merchants
GET /partner/merchant-locations
GET /partner/offers
GET /partner/publishers
GET /partner/rewards
GET /partner/transactions
DELETE /partner/user-events/{card_acount_id}
The API specification of GET /partner/offers/{offer_id}/details
is now correct.
Values associated with a cardholder have been removed. The removed values are:
merchant-locations
-> distancemerchant-locations
-> is_in_radiusis_activated
activated_at
activation_expires_at
The API specification of GET /partner/offers
is now correct.
All missing fields have been added.
The missing field display_currency is now defined in the API specification.
POST /partner/card-accounts/{card_acount_id/offers.search
POST /partner/card-accounts/{card_acount_id/offers.recommendations
POST /partner/card-accounts/{card_acount_id}/offers.details
Rather than being described as a number, activation_duration_in_days is now described as an integer.
Enhancement
The partner/card-accounts/{card_account_id}/offers.recommendations
endpoint now permits pagination with the page_offset
value.