How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

MoEngage Cards API

Operations related to fetching and deleting user cards.

MoEngage Cards API is one of 46 APIs that MoEngage publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Cards. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 2 operations across 2 paths, and defines 16 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://api-{dc}.moengage.com/v1.

2 operations 2 paths 16 schemas 1 DELETE1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api-01.moengage.com/v1
Authentication
HTTP Basic
Resource Areas
1

Authentication & Security 1

MoEngage Cards API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (basicAuth). By default, every request must be authenticated.

  • basicAuth — Authentication is done via Basic Auth. This requires a base64-encoded string of your credentials in the format 'username:password'. - Username: Use your MoEnga…

Paths & Operations 2

Across 2 paths, the API surfaces 2 operations — 1 DELETE, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Cards 2

Operations related to fetching and deleting user cards.

POST
/cards/fetch
Fetch Cards for User
fetchCards 3 params body → 200400401429500
DELETE
/cards/delete
Delete Cards for User
deleteCards 1 param body → 200400401429500

Schemas 16

The contract defines 16 schemas that model the data the API accepts and returns. The most detailed are Card (9 properties), DeleteCardsResponse (7 properties), FetchCardsResponse (7 properties), FetchCardsRequest (6 properties). Each schema is shown below with its type and property counts.

CardMetaData
object
This field contains identifiers for the card campaign, such as the campaign id, card id, and so on. For more information, refer to [Meta Data](/hc/en-us/articl…
5 properties
CardWidget
object
Widgets refer to the UI properties defined for self-handled cards. For more information, refer to [Widgets](/hc/en-us/articles/18920335915284h01H9JD2ZKP6ESH6DG…
3 properties
FetchCardsResponseData
object
2 properties
CardContainer
object
Containers contain information about the individual UI elements and their properties for self-handled cards.
5 properties
DeleteCardsRequest
object
You must provide either 'uid' or 'uniqueid'. Generating uniqueid The uniqueid refers to the device identifier and is platform-specific. [Android](https://moeng…
4 properties 1 required
CardUserActivity
object
This field contains information about the user's interaction with the card.
4 properties
Card
object
9 properties
CardAction
object
Actions define what happens when the user taps on the card. For more information, refer to [Card Actions](/user-guide/campaigns-and-channels/cards/create/creat…
4 properties
DeleteCardsPlatformResult
object
3 properties
DeleteCardsResponseData
object
3 properties
FetchCardsResponse
object
7 properties
CardDisplayControls
object
This field contains information about the display controls set in the card campaign. For more information, refer to [Display Controls](/user-guide/campaigns-an…
4 properties
ErrorResponse
object
6 properties
CardTemplateData
object
This field contains information about the Card Template. For more information, refer to [Template Data](/hc/en-us/articles/18920335915284h01H9JCXGM63ZVSPWDZZDP…
2 properties
FetchCardsRequest
object
You must provide either 'uid' or 'uniqueid'. Generating uniqueid The uniqueid refers to the device identifier and is platform-specific. [Android](https://moeng…
6 properties
DeleteCardsResponse
object
7 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

moengage-cards-api-openapi.yml Raw ↑

Other APIs MoEngage publishes across the network.

MoEngage MCP Server
MoEngage Bulk API
MoEngage Business Events API
MoEngage Campaign Reports API
MoEngage Catalog API
MoEngage Cohort Sync API
MoEngage Content Blocks API
MoEngage Coupon Files API
MoEngage Coupon Lists API
MoEngage Create Campaigns API
MoEngage Dashboards API
MoEngage Device API
Where this information came from

This is an independent, third-party profile of MoEngage Cards API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.