HTTP POST
Overview
The HTTP POST feature is used to submit data collected from your consumers via a Web Form, or to send from another system to Engage+ by means of an API Post.
The input parameters and their associated values are all contained within the header of the HTTP request, rather than in the body. This endpoint does not support authentication, nor does it support JSON or XML. The request can optionally be secured by using the HTTPS protocol. 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, 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 HTTP POST feature can optionally be used as a triggering mechanism for the deployment of an Event-triggered Campaign. When this feature is utilized in this fashion, it's typically referred to as the HTTP POST Event. See HTTP POST Event for more details.
The following diagram depicts the processing flow for loading data via the HTTP POST feature.
The HTTP POST feature requires that the following assets be defined within your Messaging account:
-
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.
POST Method
The HTTP POST feature supports the following POST operation. This feature allows you to load a record into your database. 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 - Data Management