Loyalty Engine Input Map

Input representation of the new transaction journal record simulation request.

JSON example

In the JSON, you can either provide the details of transaction journals that aren’t available in the org or a list of IDs that belong to transaction journals available in the org. If you provide the details of transaction journals that aren’t available in the org, each transaction journal’s applicable loyalty program process applies the eligible rules, executes the applicable actions, and then creates the transaction journal.

Using the transaction journal details:

1{
2  "transactionJournals": [
3    {
4      "ActivityDate": "2022-01-04T12:45:19Z",
5      "JournalDate": "2022-01-04T00:45:19Z",
6      "Brand": "",
7      "Establishment": "Apple",
8      "ExternalTransactionNumber": "P1-981950",
9      "JournalTypeId": "0lET10000004CQp",
10      "LoyaltyProgramId": "0lpT10000004CdN",
11      "MemberId": "0lMT10000004CfA",
12      "TransactionAmount": "117",
13      "TransactionLocation": "HitechCity",
14      "VoucherCode": "",
15      "Origin": "asdf",
16      "Distance": "5",
17      "Destination": "Hyderabad",
18      "FlightNumber": "SF-Ran-001",
19      "Status": "Pending"
20    }
21  ]
22}

Using the transaction journal ID:

This is supported in API version 55.0 and later.

Note

1{
2  "transactionJournals": [
3    {
4      "Id": "0lVxx00000000cj"
5    }
6  ]
7}

Properties

Name	Type	Description	Required or Optional	Available Version
`processInput`	Map<String, Object>	List of the Transaction Journal records to process and create.	Required	54.0

Loyalty Management Developer Guide

Loyalty Engine Input Map