key | value | usage |
---|---|---|
profileName |
|
Profile name to manipulate the list in |
listName |
|
List name either new, or existing. Unique. |
languageCode |
|
Language of the list must be enabled on the profile e.g. en_GB.ISO8859-15 (optional with profile default assumed) |
transactionType |
|
CREATE | APPEND | REPLACE |
emailCol |
|
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 |
|
mobile column index (optional if emailCol provided) |
responseType |
|
EMAIL | HTTP | REST : How to send the list upload completion notification |
responseUri |
|
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 |
|
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 |
|
Security Token authentication (enabled within the platform via my account -> edit details -> enable -> generate)(optional) |
type | code | content : string |
---|---|---|
Success | 200 | OK : Integer (Where the integer is the transactionID used in the data upload |
Error | 200 | Error : Error Message |
key | value | usage |
---|---|---|
profileName |
|
Profile name to manipulate the list in |
transactionId |
|
The transactionId returned from list_upload_meta |
file |
|
valid CSV file (list) to upload |
type | code | content : string |
---|---|---|
Success | 200 | OK : Integer (Where the integer is the transactionID used in the data upload |
Error | 200 | Error : Error Message |
curl
--data "profileName=TestProfile&listName=NewList&transactionType=CREATE&emailCol=0&responseType=EMAIL&responseUri=test@pure360.com&COL_first_name=1" 'https://response.pure360.com/interface/list_upload_meta.php'
Send a request to the list upload meta processor, in this case adding the NewList to the profile TestProfile, and CREATEing it, the first column of the CSV that will get sent across contains the email address and the next column contains the first name. When the list upload process completes, a notification EMAIL is sent to test@pure360.com.
If this has processed correctly the response should be OK : XXXX where XXXX is a transactionId.
curl
--form "profileName=TestProfile"
--form "transactionId=XXXX"
--form "file=@//usr/FilePath/file.csv"
'https://response.pure360.com/interface/list_upload_data.php'
Send a request to the list upload data processor, in this case sending the file in usr/FilePath/file.csv to profile TestProfile and reference the container for this as the XXXX transaction ID returned from the meta request.
Target list | csv | Field mapping in post |
---|---|---|
|
File has 4 columns: |
|
Target list | csv | Field mapping in post |
---|---|---|
|
File has 4 columns: |
|
Target list | csv | Field mapping in post |
---|---|---|
|
File has 4 columns: |
|
Target list | csv | Field mapping in post |
---|---|---|
|
File has 2 columns: email and post code |
Each COL_ is listed in order, non-existent column numbers have been mapped for the list fields which are not present in the list |
Target list | csv | Field mapping in post |
---|---|---|
|
File has 2 columns: email, abandon. |
Each COL_ in the list is listed in order, non-existent column numbers have been mapped for the list fields which are not present in the list |
Open Postman, import as 'raw text' and save for an easy test suite.
Make sure you copy the transactionId from the Meta post. You will not get issued another one until you use the current open one or wait 12 hours for it to be cleared down. If you are in a pickle ask your account manager, they might be able to get it reset earlier.
curl --location --request POST 'https://response.pure360.com/interface/list_upload_meta.php' \
--header 'Content-Type: application/x-www-form-urlencoded' \
--data-urlencode 'profileName=myProfile' \
--data-urlencode 'listName=autolistTest1' \
--data-urlencode 'transactionType=APPEND' \
--data-urlencode 'emailCol=0' \
--data-urlencode 'responseType=EMAIL' \
--data-urlencode 'responseUri=myEmail' \
--data-urlencode 'token=[upload token from profile]' \
--data-urlencode 'COL_1=1' \
--data-urlencode 'COL_2=99' \
--data-urlencode 'COL_3=3' \
--data-urlencode 'COL_4=2'
curl --location --request POST 'https://response.pure360.com/interface/list_upload_data.php' \
--form 'profileName="myProfile"' \
--form 'transactionId="[transactionId from Meta]"' \
--form 'file=@"/Users/me/Data/file.csv"'