Update Campaigns

This API can be used to update a campaign in MoEngage.

info	Information Currently, you can use this API to update Email campaigns only. You can update only those Email campaigns that are created using the Create Campaigns API, not the campaigns created through the MoEngage Dashboard.

API Endpoint

PATCH https://api-0X.moengage.com/core-services/v1/campaigns/{{campaign_id}}

Each customer is hosted on a different data center; you can find your data center number (value of X) by checking the data center and API endpoint mapping page.

Authentication

The API request will be authenticated through Basic Authentication. Basic Authentication sends a Base64-encoded string containing your username and password with every API request. It encodes a 'username:password' string in Base64 and appends the encoded string with 'Basic '. This string is included in the authorization header as shown below:

{"Authorization":"Basic bmF2ZWVua3VtYXI6bW9lbmdhZ2U="}

You can obtain the username and password details from the MoEngage Dashboard.

Navigate to Settings -> Account -> APIs.
Copy the following details:
- Username: Under Workspace ID (earlier app id), click the copy icon to copy the username.
- Password: In the API keys section, click the copy icon in the Campaign report/Business events/Custom templates tile to copy the API key.
Use these details to authenticate the API requests.

Request Headers

Key

Required

Sample Values

Description

Content-Type

Required

{"Content-Type": "application/json"}

Set the Content-Type header to application/json.

Authorization

Required

{"Authorization": "Basic bmF2ZWVua3VtYXI6bW9lbmdhZ2U=="}

This authentication parameter, used for access control, must be passed in the request. To generate the authentication header, refer to Authentication.

MOE-APPKEY

Required

{“MOE-APPKEY”: “Workspace ID”}

This is the workspace ID (earlier APP ID) of your MoEngage workspace. The MOE-APPKEY has to be passed in the request. You can find your MoEngage Workspace ID in the MoEngage Dashboard:

Settings -> Account -> APIs -> Workspace ID (earlier app id)

For more information, refer to Authentication.

Request Body

info

Information

To update an Email campaign, pass only those objects and fields that you want to update. For example, if you want to update the content of the Email campaign, pass only the campaign_content object. You need not pass the complete payload.
If you want to update one field of a campaign, you must pass the complete object to which the field belongs. For example, to update the "Subject" of the email, pass the complete campaign_content object.
You can update fields in the campaign when the campaign is in any state apart from Stopped and Archived. You can see the campaign status on the All Campaigns page, by searching the campaign ID. You can also get the Campaign Status by querying the GET Campaign details API with Campaign ID.
You can edit all fields except scheduling type if the campaign is in a Scheduled state for:
- One-time campaigns
- Periodic or Event-triggered campaigns if a single instance has not been sent out yet
If the campaign is in the Active state, you cannot edit the following fields:
- Trigger Condition
- Segmentation Details
- Conversion Goal Details
- Scheduling Type
- Scheduling Start Date

Key	Required	Values	Description
basic_details	Optional	JSON Object	This object contains the basic details of the campaign. For more information, refer to Basic Details.
campaign_content	Optional	JSON Object	This object contains the campaign content. For more information, refer to Campaign Content.
connector	Optional	JSON Object	This object contains the connector details. For more information, refer to Connector Details.
control_group_details	Optional	JSON Object	This object contains the control group details. For more information, refer to Control Group Details.
conversion_goal_details	Optional	JSON Object	This object contains the conversion goal details. For more information, refer to Conversion Goal Details.
delivery_controls	Optional	JSON Object	This object contains the delivery controls details. For more information, refer to Delivery Controls.
utm_params	Optional	JSON Object	This object contains the UTM parameters details. For more information, refer to UTM Parameters.
request_id	Required	String	This field denotes the request ID for which the campaign is updated.
scheduling_details	Optional	JSON Object	This object contains the scheduling details. For more information, refer to Scheduling Details.
segmentation_details	Optional	JSON Object	This object contains the segmentation details. For more information, refer to Segmentation Details.
trigger_condition	Optional	JSON Object	This object contains the trigger condition details. For more information, refer to Trigger Conditions.
updated_by	Required	String	This field denotes the Email ID of the user who updated the campaign. Supported value is email ID only.

Response

Key

Data Type

Description

message

String

This field contains a brief description of the request status in the case of success.

error

JSON Object

This field contains the reason for the request's failure.

Structure:

"error": {

"code": "<error_code>",

"message": "<error_message>",

"target": "<target>",

"details": [

{

"target": "<target>",

"message": "<error_message>"

}

"request_id": "<request_id>"

}

The error object contains the following fields:

code - This field is of String type and contains the error code that provides a brief explanation of the error. For example, 400 - Bad Request, 401- Authentication required, and so on. This field is present in the response only in the case of errors.
message - This field is of String type and describes why the request has failed.
target - This field is of String type and denotes the target of the error.
details - This object provides the error details and contains the following information:
- target - This field is of String type and denotes the target of the error.
- message - This field is of String type and describes why the request has failed.
request_id: This field denotes the request ID.

Response Codes

Status Code	Request State	Description
204	Success	The server successfully processed the request, but is not returning any content.
400	Bad Request	This response is returned when the required parameters are missing from the request, or when the provided parameters are invalid, or when a template already exists with the same version, name, or id.
401	Authentication Failure	This response is returned when the authorization parameters are missing in the HTTP Auth Header.
500	Internal Server Error	This response is returned when the system runs into an unexpected error.

Sample cURL Request

The following is a sample code to update the segmentation details of a campaign:

curl --location --request PATCH 'https://api-0X.moengage.com/core-services/v1/campaigns/{{Campaign_ID}}' \
--header 'MOE-APPKEY: {{Workspace_ID or APP_ID}}' \
--header 'Content-Type: application/json' \
--header 'Authorization: Basic {{Authorization_Key}}' \
--data-raw '{
    "updated_by": "john.doe@example.com",
    "request_id": "34423",
    "basic_details": {
        "name": "edited one time campaign edited",
        "tags": [
            "engagement",
            "all users"
        ],
        "user_attribute_identifier": "John",
         "segmentation_details": {
        "included_filters": {
            "filter_operator": "and",
            "filters": [
                {
                    "data_type": "string",
                    "category": "Tracked Standard Attribute",
                    "name": "uid",
                    "value": "John_Ios",
                    "filter_type": "user_attributes",
                    "case_sensitive": false,
                    "operator": "is",
                    "negate": false
                }
            ]
        }
    }
    }
}
'

Sample Response

info	Information For a successful response of 204, the API does not return any content.

[]

{
    "error": {
        "code": "400 Bad Request",
        "message": "request_id key is mandatory field",
        "target": "request_id",
        "details": [
            {
                "target": "request_id",
                "message": "request_id key is mandatory field"
            }
        ],
        "request_id": "11"
    }
}

{
    "error": {
        "code": "401 Authentication error",
        "message": "Authentication required",
        "details": [
            {
                "code": "InvalidValue",
                "target": "APP_SECRET_KEY",
                "message": [
                    {
                        "code": "InvalidValue",
                        "target": "APP_SECRET_KEY",
                        "message": "Invalid APP_SECRET_KEY is provided."
                    }
                ]
            }
        ],
        "request_id": ""
    }
}

{
    "error": {
        "code": "500 Internal Server Error",
        "message": "Something went wrong. Please contact Moengage team",
        "target": "string",
        "details": [
            {
                "message": "Expecting value: line 1 column 1 (char 0)",
                "target": ""
            }
        ]
    }
}

Postman Collections

We have made it easy for you to test the APIs. Click here to view it in Postman.

FAQs

arrow_drop_down Can I update the segmentation audience when the campaign is in Active state?

No, you cannot update the segmentation audience after the campaign is in Active state. You can update the segmentation audience if the campaign is in Scheduled state or create a duplicate by stopping the existing campaign to pass new segmentation details.

arrow_drop_down When does the updated campaign start sending out to the users?

The updated campaign starts sending out as soon as changes are done except for Event-triggered campaigns. In Event-triggered campaigns, details are cached and take up to 30 mins to send the updated campaign.

arrow_drop_down How can I fetch the campaign ID of the campaign to be updated?

You must call the "GET" API by the campaign name, channel, or any other filters to fetch the campaign ID of the desired campaign. For more information, refer to Get Campaign Details.