Content APIs Overview

A content API is an external endpoint that MoEngage calls to pull dynamic data into a campaign at send time. For example, you can use one to fetch the current weather in a user’s city, the live price of an item in their cart, or the status of their flight. The MoEngage Content APIs allow you to list the content APIs configured in your workspace and test a saved configuration against its upstream endpoint. To create or edit a content API, use the MoEngage dashboard. For more information, see Add a Content API.

​

Endpoints

The Content APIs are a collection of the following endpoints:

• List Content APIs: Returns all content APIs in the workspace, or a single one specified by name or ID.
• Test Content API: Calls the upstream endpoint of a saved content API and returns the response.

​

Authentication

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.

​

Personalization Tokens

A content API configuration can include Jinja tokens in its URL, parameters, headers, or body. Tokens are grouped by namespace — for example, {{UserAttribute['city']}} or {{EventAttribute['name']}}. When you test a configuration, supply sample values for these tokens in the dynamic_values object of the request body, keyed by namespace. A token like {{UserAttribute['city']}} resolves from dynamic_values.UserAttribute.city. MoEngage resolves every token before calling the upstream endpoint. Omit the request body if the configuration has no tokens.

​

Pagination

List Content APIs returns at most 20 items per page. Treat the cursor as opaque — do not decode or modify it. To page through every content API in the workspace:

1. Request the first page with limit alone.
   First Page

   curl --request GET \
     --url 'https://api-01.moengage.com/v5/content-apis?limit=20' \
     --header 'Authorization: Basic <base64(workspaceId:apiKey)>'
   
2. Check pagination.has_more in the response. When it is true, send the same request again with pagination.next_cursor passed back as the cursor parameter, keeping limit unchanged.
   Next Page

   curl --request GET \
     --url 'https://api-01.moengage.com/v5/content-apis?limit=20&cursor=eyJsYXN0X2lkIjoiNjZiM2QxZTBmMmE0YzU4ZTlkN2IzYzIxIn0=' \
     --header 'Authorization: Basic <base64(workspaceId:apiKey)>'
   
3. Repeat step 2 until pagination.has_more is false.

​

FAQs

​

Manage Content APIs

​

Test Content APIs

​

Postman Collection

Test these endpoints using our pre-configured Postman collection: View MoEngage Content APIs Collection.