HTTP POST Event
Overview
The HTTP POST endpoint is used to submit data collected from your consumers via a Web Form, or from another system via an API Post. The Web Form can either be hosted on the Messaging platform, or hosted externally on some other site. Only one record can be submitted per API request. The input parameters and their associated values are all contained within the header of the HTTP request, rather than the body.
When defining an Event-triggered Campaign, the platform allows you to use that HTTP POST request as the triggering mechanism. Upon submission of the designated Web Form or API Post, the system will deploy the Campaign. The platform will load or update the database prior to deploying the Campaign, which allows you to use data from your database when building your message content.
This endpoint does not support authentication, nor does it support JSON or XML. The request can optionally be secured by using the HTTPS protocol, as long as the correct Customer ID and Form ID are provided, and the right field names are posted to the Form. If using HTTPS, please note that the connection is encrypted, but the data being passed is not encrypted.
For more details on how to set up an HTTP POST Event, please see the HTTP POST Technical Guide.
The URLs for this feature are:
North America: https://ats.eccmp.com/ats/post.aspx?cr=[xxx]&fm=[xxx]&[data fields]
Europe: https://ats.eccmp.eu/ats/post.aspx?cr=[xxx]&fm=[xxx]&[data fields]
Japan: https://ats.eccmp.jp/ats/post.aspx?cr=[xxx]&fm=[xxx]&[data fields]
The following diagram depicts the processing flow for deploying a Campaign via the HTTP POST endpoint.
Pre-requisites
The HTTP POST Event requires the following:
Data Map -- The Data Map provides data handling instructions, such as where to store the inbound data contained within the request message, whether this data should be used to update existing records and / or create new records, and any optional formatting or special processing to perform on the inbound data.
API Post -- If data is being submitted from another system, then you must create and publish an API Post within Messaging. The API Post defines all the expected fields in the request message, and provides support for custom response messages and a schedule. Please note that the API Post must have the "REST API Only" option and the "Triggered" option both unchecked.
Web Form -- If recipients are submitting data via a Web Form, then you must create and publish the Web Form. Web Forms provide a user-friendly, front-end interface for your customers to enter their information. The Web Form can optionally be hosted within the Messaging platform, or within your system, or on some other third-party system.
Campaign -- You must define and launch an Event-triggered Campaign that uses either the above API Post, or the above Web Form, as the trigger type.
POST Method
The HTTP POST Event feature supports the following POST operation. This feature allows you to load a record into your database, and trigger the deployment of an Event-triggered Campaign. The request must include the following:
Your Customer ID
The Form ID of the Web Form or API Post.
The data to be loaded, sent using Name / Value pairs. For the field names, be sure to use the system Column Name, and not the "Display Name."
For example:
https://ats.eccmp.com/ats/post.aspx?cr=394&fm=2678&s_email=johndoe@cheetahdigital.com&s_name_first=John&s_name_last=Doe
Back to API Category - Campaign Deployment