Validate Campaign (V5)

Runs full publish-time validation (DRAFT_PUBLISH) on a saved draft without mutating it. Returns valid: true if the campaign would pass, or a list of blocking errors if it would not.

All campaign data is read from the saved draft identified by campaign_id in the path. There is no channel-specific payload.

POST /v5/campaigns/{campaign_id}/validate

Validate Campaign (V5)

cURL

curl --request POST \
  --url https://api-{dc}.moengage.com/v5/campaigns/{campaign_id}/validate \
  --header 'Authorization: Basic <encoded-value>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "request_id": "{{request_id}}"
}
'

200

valid

{
  "response_id": "abc-501",
  "type": "campaign",
  "data": {
    "valid": true
  }
}

You do not need an idempotency key for this endpoint. The validate endpoint is read-only and safe to retry freely.

Validation Modes

The V5 API applies validation in two modes:

Mode	Triggered by	Strictness
Lenient	Draft create (POST /v5/campaigns) and component patch (PATCH /v5/campaigns/{id})	Partial — individual components are validated in isolation as they are written
Full (DRAFT_PUBLISH)	POST /v5/campaigns/{id}/validate and publish	Strict — all components are validated together as a complete, publish-ready campaign

Use this endpoint to catch DRAFT_PUBLISH failures before triggering a publish.

Validation Failures

All validation failures are blocking. There is no warning or non-blocking tier. A campaign that fails validation returns valid: false with a list of field-level errors. Each error identifies the field path and the issue.

Channel-Specific Rules

The following rules are enforced at DRAFT_PUBLISH for each channel:

Push

• campaign_content must be present and include content for all platforms listed in basic_details.platforms.
• template_type must be valid for the target platform (Android, iOS, Web).
• Platform-specific required fields (for example, title and message for Android basic templates) must be non-empty.

Email

• connector.connector_type and connector.connector_name must be present and match a connector configured in your workspace.
• basic_details.from_address must be set and match a verified sender in the configured connector.
• basic_details.subscription_category must be present for PROMOTIONAL content type.
• campaign_content must include at least one variation with a non-empty subject and html_content.

Delivery-Type-Specific Rules

The following rules are enforced at DRAFT_PUBLISH based on campaign_delivery_type:

Delivery Type	Additional Requirements
ONE_TIME, PERIODIC	scheduling_details must be present.
AT_FIXED_TIME scheduling	scheduling_details.timezone must be present.
PERIODIC	scheduling_details.periodic_details must be present with a valid sending_frequency.
EVENT_TRIGGERED	trigger_condition must be present with at least one included_filters entry.
DEVICE_TRIGGERED	trigger_condition must be present. Trigger delay fields (trigger_delay_type, trigger_delay_value, trigger_delay_granularity) must not be set — they are only valid for EVENT_TRIGGERED.
BUSINESS_EVENT_TRIGGERED	basic_details.business_event must be present.
LOCATION_TRIGGERED	basic_details.geofences must contain at least one valid geofence entry.

Rate Limits

Rate Limit Name	Rate Limit
Validate campaign per second	The total number of validate campaign requests per second per client allowed is 10.
Validate campaign per minute	The total number of validate campaign requests per minute per client allowed is 100.
Validate campaign per hour	The total number of validate campaign requests per hour per client allowed is 6000.

Authorizations

Authorization · string · header · required

Authentication is done via Basic Auth. This requires a base64-encoded string of your credentials in the format username:password.

• Username: Use your MoEngage Workspace ID (also known as the App ID). Find it in the MoEngage dashboard at Settings > Account > API keys.
• Password: Use an API key from Settings > Account > API keys.

Refer to API Key Dashboard for details on creating and managing API keys.

Headers

MOE-APPKEY · string

Your MoEngage Workspace ID (App ID). Optional — Basic Auth already carries the Workspace ID as the username, so this header is not required. Find it in the dashboard at Settings > Account > API keys.

X-MOE-Request-Id · string

Client-supplied trace ID for tracing. Correlates with response_id. Supply this header or request_id in the body; if both are set, they must match.

Path Parameters

campaign_id · string · required

Raw 24-char ObjectId of the campaign to validate. Use the id value returned in the Create Campaign response.

Body

application/json

request_id · string

Optional string (UUID v4 recommended) used to identify this validation call. Unlike other POST endpoints, this field is not required and does not enforce deduplication - the validate endpoint is read-only and safe to retry freely.

Example:

"{{request_id}}"

Response

200

application/json

Validation result - always returned regardless of whether the campaign passes or fails validation.

response_id · string

type · string

Example:

"campaign"

data · object

• When valid is true, only valid is returned.
• When valid is false, errors lists one or more field-level issues found during publish-time validation (DRAFT_PUBLISH).

Show child attributes