Skip to main content
GET
SMS campaigns: SMS campaigns are returned by this endpoint; the response channel field will be SMS. The connector and sender_name fields carry SMS-specific details. SMS campaigns can be retrieved but must be created and managed through the MoEngage dashboard or V1 APIs in the interim.

Rate Limits

Notes
  • Breaching the limits will reject the request.
  • Per-hour limits use a rolling window of the last 1 hour.

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). You can find it in the MoEngage dashboard at Settings > Account > APIs > Workspace ID (earlier app id).
  • Password: On your MoEngage workspace, navigate to SettingsAccountAPI keys and click Create new key. The tab lists every API surface (Data, Segmentation, Push, Email, Campaigns, Templates, and more) and exposes per-resource actions. For Campaigns, ensure the View, Create & Manage, and Create, Manage & Publish checkboxes are selected.

For more information on authentication and getting your credentials, refer to Getting your credentials.

Send the value in the Authorization header as Basic followed by Base64-encoding of appkey:apisecret (workspace ID and API key).

Headers

MOE-APPKEY
string
required

Your MoEngage Workspace ID (App ID). Find it in the dashboard at Settings > Account > APIs > Workspace ID.

X-MOE-Request-Id
string
required

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 retrieve.

Response

Campaign details retrieved successfully.

response_id
string
type
string
Example:

"campaign"

data
object

Detailed information about a campaign returned by GET /v5/campaigns/{campaign_id} and POST /v5/campaigns/search.

Identifier change from V1 to V5:

  • In V1, the campaign identifier was returned as campaign_id. In V5, it is returned as id.
  • The legacy campaign_id field may also be present alongside id for backward compatibility, but id is the canonical V5 identifier.

V1 fields preserved in V5 under the same names: created_by, updated_by, created_at, updated_at, sent_time, flow_id, flow_name, parent_id, connector, utm_params, campaign_audience_limit.