Fetches the subscription category preferences information for a specific user based on the encrypted User ID and Campaign ID found in the landing page URL.
user_id (MoEngage ID) and the cid (Campaign ID) fields should be fetched from the landing page URL.
For example, if the link to the custom landing page was https://www.abc.com/managepreference, when the user clicks the same from the email, the link will look like this:
user_id and cid to pass to the API.This authentication parameter, used for access control, must be passed along with the request. To generate the authentication header, refer to Authentication.
It uses Workspace ID as username and Data API Key as password.
This is your MoEngage account's APP ID that has to be passed along with the request. You can find your MoEngage Workspace ID at Settings -> Account -> APIs -> Workspace ID (earlier app id).
Set the Content-Type header to application/json.
This is the MoEngage ID that uniquely identifies the customer for whom the subscription preferences are being updated.
Note: MoEngage ID is encrypted using 16 bits DES and is encoded in the URL of the landing page. It must be sent as-is (encrypted).
This is the campaign id of the email campaign. This field contains the information about the email campaign received by the customer.
Note: The campaign ID is encrypted using 16-bit DES and is encoded within the landing page URL. You must fetch the encrypted <campaign Id> from the URL and send it directly to MoEngage; it is not necessary to perform any decryption.
Success. This response is returned when the request is processed successfully.
A JSON Object that contains the subscription preferences of the customer.
category_name is the unique category name in MoEngage.
{
"Promotions": true,
"Updates": false,
"Recommendations": true,
"Newsletter": false
}