Import Using XML Error

[daveguderian]

I am attempting to do my first import into an application using a http import. The import application needs the data in XML format (which I have not done before), and I am receiving an error (appears related to my post body, but not 100% sure). I am not sure if this is tied to the formatting of my XML, or something different.

Here is the XML code I am using for import (cc information is test data):

    add_customer
    {{connection.http.encrypted}}
    5431111111111111
    1025
    
    
    
    {{record.IntPS__First_Name__c}}
    {{record.IntPS__Last_Name__c}}

Here is the error I am receiving when I try to import:

Additionally, here is the webpage outlining the data elements:

https://secure.networkmerchants.com/gw/merchants/resources/integration/integration_portal.php#cv_variables

Any help is greatly appreciated!

[tylerlamparter]

@daveguderian {{connection.http.encrypted}} is invalid. It should be something like {{connection.http.encrypted.security_key}} or however you stored it in your encrypted fields section.

[daveguderian]

Thanks Tyler. I appreciate the help on this.

Another question I have is that I have an API where the "POST" information needs to be in the URL Params as displayed below in Postman. Where would these same keys be entered in Celigo?

[tylerlamparter]

@daveguderian parameters are just put in the relative uri field just as you see in postman uri field in your screenshot.

[daveguderian]

Thanks so much Tyler. So my next question is how should I send the security_key. In postman I am sending it via the Query Params, but it doesnt actually show up in the actual relative URI in Postman (as you can see from the initial screenshot).

How do I replicate that in Celigo as Celigo is automatically adding it to the end of the URI?

[kellyizer]

Dave,

You can put that info in the HTTP encrypted field and then call it with handlebar statement as Tyler stated before in the relative URI

{{connection.http.encrypted.security_key}}

[tylerlamparter]

@daveguderian you should probably just use settings on the connection level so you don't have to specify this connection key on every export and import.