What application developers do for transactional message

Application developers create the local transactional message client that submits transactional message requests to the Unica Deliver Transactional messaging Service (TMS). The local transactional message client application processes each transactional message message by making a REST or a SOAP request to the Deliver TMS over an HTTPS connection.

Working with Deliver TMS using REST APIs

Unica provides REST API documentation for Transactional messaging service under Settings > Messaging Settings section of Unica application. It explains how API can be invoked, how user can authenticate for calling this API, what input headers and request payload need to be provided to call this API and what response is returned by this service.

Payload for REST API is very similar to the one for SOAP service, so you can relate closely request object need to be formed for REST service with details provided in this documentation on how to prepare request object for SOAP client.

Also, if you already have coded SOAP client for interacting with Deliver TMS, migrating to REST will not be a very difficult task.

Working with Deliver TMS using SOAP APIs

Unica provides a WSDL to allow developers to design the web service request. For more information about the WSDL, see WSDL for Deliver transactional email.

Creating the local transactional message client application requires coordination between application development team responsible for corporate transaction systems and the digital marketing team. Digital marketers provide information about the transactional message messages and attachments that are to be sent as transactional message.

The following table lists the activities that application developers must perform.

Developer responsibilities for transactional messaging.
Activity	Description
Build the transactional monitoring systems required to detect the types of transaction events that trigger transactional message.	Consult with the Digital marketing team to determine which business or customer activities qualify as suitable transaction events.
Code or configure a local transactional message client application to connect to the Deliver TMS and submit web service requests in response to specified transaction events. The client must be able to provide access credentials for your hosted message account.	Review Transactional Message service API documentation in Settings -> Messaging Settings section of Unica application if you plan to use REST APIs for transactional messages. Review the WSDL and sample transactional message client examples provided byUnica for guidance.
Structure web service requests to provide personalization information as name-value pairs. The request must also specify the data type for each personalization field.
Consult with the digital marketing team to determine if sending email attachments is a requirement.
Coordinate with the digital marketing team to identify the sources for the personalization required by the transactional email messages and attachments.	The transactional message client must be able to connect to the business systems and databases that provide personalization values in the transactional message request.
Design and code error handling.	Code the client to handle errors reported by the Deliver TMS. Include features to notify administrators if the client cannot connect or if web service requests fail. For information about error codes returned by the Deliver TMS, see AdvisoryMessage.
Coordinate with the digital marketing team to test the integration of the local transactional message client with the Deliver TMS.	Digital marketers need to enable messagings for transactional message testing and specify test addresses. Application developers need to devise ways to simulate the target transactional events and provide expected transaction and personalization information to the local transactional message client.