Get Campaign (V5)
Returns the full configuration and current status of a single campaign by its ID.
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
- Breaching the limits will reject the request.
- Per-hour limits use a rolling window of the last 1 hour.
Authorizations
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
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.
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
Raw 24-char ObjectId of the campaign to retrieve.
Response
Campaign details retrieved successfully.
"campaign"
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 asid. - The legacy
campaign_idfield may also be present alongsideidfor backward compatibility, butidis 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.