Transact XML How do I submit data to Transact? (For Developers) Note: This section provides details about Transact Submissions. It is intended for Developers. Silverpop uses an XML API (Extended Markup Language Application Programming Interface) to submit transaction activity and email responses. The API is intended for integration with backend systems. The user can submit mailing requests to Transact through XML (Extensible Markup Language) using two submission methods: HTTP(S) and (S)FTP. HTTP Submission: Data is passed to the Transact server via the HTTP(S). This is limited to 10 contacts. FTP Submission: Data is passed to the transact server via XML over (S) FTP. This can include 10 to 5000 contacts. About HTTP Submissions You can use HTTP to transfer files from a Web server to the contact’s Web browser, allowing contacts to view a mailing as a Web page. HTTP submissions are processed and sent immediately. You should send submissions with less than 10 contacts for HTTP processing rather than FTP, due to possible delays caused by networks. Here's how it works: Data is passed to the Transact server via XML over HTTP. The Transact server then parses the XML and populates the personalization codes in the mailing template with the data provided. Transact sends the mailing to the contact and saves the information in the database. Finally, a response string is returned to the submission IP. HTTP Submit Address The HTTP Submit Address is the IP address from which an organization sends the XML Submit document using HTTP. It is set up in the Organization Administration menu in Engage. Documents can contain multiple contacts, but submissions with less than 10 contacts are preferred for HTTP processing, due to possible delays caused by networks. HTTP submissions are processed and sent immediately. Submit-to URL: http://engage[X].silverpop.com/XTMail (insert your pod in place of [X]) 38 www.silverpop.com 1-866-SILVPOP (745-8767) © 2012 Silverpop Systems Inc. All rights reserved.
Transact XML Note: Transact uses IP-level validation for security purposes to ensure no other sources can send messages. You can also use SSL. The following table shows Engage URLs and their corresponding HTTP address. Engage URL http://engage1.silverpop.com http://engage2.silverpop.com http://engage3.silverpop.com http://engage4.silverpop.com http://engage5.silverpop.com HTTP Submit Address http://transact1.silverpop.com/XTMail http://transact2.silverpop.com/XTMail http://transact3.silverpop.com/XTMail http://transact4.silverpop.com/XTMail http://transact5.silverpop.com/XTMail HTTP Response Address The HTTP response address replies to the submitter IP address. HTTP Submission Methods Individualized Personallization: • Mailing template is static, except for personalizations • Personalizations are populated by data supplied in the XML file • Faster transmissions and sends due to smaller file • majority of content contained in Transact mailing Template. SPAM check is available • HTML passed with this method must be wrapped with CDATA tag 39 www.silverpop.com 1-866-SILVPOP (745-8767) © 2012 Silverpop Systems Inc. All rights reserved.
Transact XML 10. Exception:javax.xm
Transact XML 1 - encountered errors
Transact XML XML Submission Documen
Transact XML FLT_2_TRIP_TITLE Sal
Transact XML font-weight: bold; fon
Transact XML Thursday, February 23
Transact XML Transac
Transact XML Maintenance About Main
Transact XML Troubleshooting About
Transact XML Hyperlinks and Trackin