Indexes start with the left most column at 0, incrementing by 1 moving right per column across the CSV
key |
value |
usage |
profileName |
"profileName"
|
Profile name to manipulate the list in |
listName |
"Master+List"
|
List name either new, or existing. Unique. |
languageCode |
"en_GB.ISO8859-15"
|
Language of the list must be enabled on the profile e.g. en_GB.ISO8859-15 (optional with profile default assumed) |
transactionType |
"CREATE"
|
CREATE | APPEND | REPLACE |
emailCol |
0
|
During a CREATE / REPLACE this value referes to the email column index in the CSV file (optional if mobileCol provided) During an APPEND the email address MUST be in column 0 of the CSV file |
mobileCol |
1
|
mobile column index (optional if emailCol provided) |
responseType |
"EMAIL"
|
EMAIL | HTTP | REST : How to send the list upload completion notification
|
responseUri |
"test@test.com"
|
The address to send the notification to, either email address or URI. If IGNORE is given as the responseType it is recommended to use a string value such as 'FALSE', 'NULL' or 'NONE' as the value for maintainability purposes
|
COL_field1 |
2
|
During a CREATE / REPLACE the field1 is the name to give the custom data field in the contact list, the value is the index of this field both in the CSV and the custom data field index in the contact list. During an APPEND the field1 refers to the existing custom data field name in the contact list, and the value refers to the custom data field index in the contact list. Therefore the field order in the CSV file uploaded (during the data request) MUST be in the order for the APPEND that they were during the CREATE. |
token |
"d82c69cd7a21a2c569db960b528d7ae53e6b45748fe2237a4f146fcd80a4fd56"
|
Security Token authentication (enabled within the platform via my account -> edit details -> enable -> generate)(optional) |