This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
api-automation [2017/01/20 14:27] ben [Response] |
api-automation [2018/02/19 11:21] benc |
||
---|---|---|---|
Line 23: | Line 23: | ||
When preparing the Emails to use in your Autoresponder, you can manually enter "Transaction Data" Mergefields into the Email content where you'd like to merge in values from this JSON data. | When preparing the Emails to use in your Autoresponder, you can manually enter "Transaction Data" Mergefields into the Email content where you'd like to merge in values from this JSON data. | ||
- | The syntax for Transaction Data Mergefields is <nowiki>{{trx:MergefieldName}}</nowiki> and "MergefieldName" must exactly match the name in the JSON data. You can also include a default value which is used if either the property isn't found in the JSON data or its value is blank, e.g. <nowiki>{{trx:DiscountCode default=n/a}}</nowiki> | + | The syntax for Transaction Data Mergefields is <nowiki>{{trx:MergefieldName}}</nowiki> and "MergefieldName" must match the name in the JSON data. You can also include a default value which is used if either the property isn't found in the JSON data or its value is blank, e.g. <nowiki>{{trx:DiscountCode default=n/a}}</nowiki> |
The JSON data must describe a single "flat" object (i.e. one consisting only of name/value pairs as shown in the example below), it cannot be an array. | The JSON data must describe a single "flat" object (i.e. one consisting only of name/value pairs as shown in the example below), it cannot be an array. |