Transaction Journals Simulation

Runs a simulation to determine how transaction journals are processed against their corresponding loyalty program processes. When transaction journals meet the criteria and conditions for a program process, actions that are set up in the process are triggered for the transaction journals.

To use this resource, your org must have either B2C - Loyalty, B2C - Loyalty Plus, Loyalty Management - Growth, or Loyalty Management - Advanced license enabled, and you must be assigned the Loyalty Management permission set.

55.0

No

POST

Root XML Tag

<loyaltyEngineInput>

JSON Example

Some of the API request fields contain field names that are interchangeable. For information on the list of interchangeable field names, see Loyalty Management Connect API Interchangeable Request Fields.

Here’s a sample request to pass loyalty engine runtime details.

To enforce promotion limits, include the appliedPromotions array inside each transaction journal entry in the request. Promotion limits are not evaluated if this array is absent. Use the Eligible Promotions List (POST) resource to retrieve the list of promotions that haven’t reached their limit, and pass the result as appliedPromotions. For coupon-based promotions with usage limits, also set shouldCheckCouponUsageLimit to true at the top level of the request.

Provide contactId to retrieve rewards related to a Person Account.

Using the transaction journal ID:

Sample payload to retrieve rewards assigned to accounts.

Properties

NameTypeDescriptionRequired or OptionalAvailable Version
shouldCheckCouponUsageLimitBooleanIndicates whether the coupon usage limit check is enabled.Required62.0
transactionJournalsLoyalty Engine Input MapRepresents the transaction journals records to process.Required54.0
runSettingLoyalty Engine Run Settings InputLoyalty runtime setting to run the simulation on the transaction journals.Required for simulation, otherwise optional55.0

Loyalty Engine Realtime Output