Delete Cards for User
Delete specific card campaigns for a user by uid or unique_id from the MoEngage Cards database.
Rate Limit
The rate limit is 50K RPM (Requests Per Minute) and is applicable at the DB (App) level.Generating unique_id
Theunique_id refers to the device identifier and is platform-specific. You can generate the unique id for Android and iOS using the methods listed below.
- Android
- iOS
FAQs
What is the difference between unique_id and uid? The unique_id is the unique value that identifies the user to whom the cards need to be deleted. It is a platform-specific device identifier that can be generated, as mentioned in the Generating unique_id section. The uid is the unique MoEngage Standard ID that identifies the user.Authorizations
Uses Workspace ID as username and API Key (from Campaign report/Business events/Custom templates tile) as password. To generate the authentication header, refer to Authentication.
Headers
Your MoEngage Workspace ID. Found in Settings > Account > APIs.
Body
Must provide either 'uid' or 'unique_id'.
List of campaign IDs whose cards should be deleted for the user. In the case of a periodic campaign, if the campaign ID of the parent campaign is specified, the cards will get deleted for the child campaigns as well.
The uid is the unique MoEngage Standard ID (Email ID Standard or Mobile Number Standard) that identifies the user.
The unique_id is the platform-specific device identifier. Refer to Generating unique_id for details.
Specify platforms to delete cards from. If omitted, the cards specified for deletion will be deleted from all the platforms they are associated with. Allowed Values: ANDROID, IOS, WEB
ANDROID, IOS, WEB, android, ios, web Response
This response is returned when the request is processed successfully.
This field represents whether the request was successful and contains true when the request was successful and false otherwise.
Unique identifier that denotes the request.
This field contains the platform-specific results of the delete operation.
This field is present in the response body only when the request is unsuccessful and contains the error type.
This field is present in the response body only when the request is unsuccessful and contains the error description.
This field is present in the response body only when the request is unsuccessful and contains the error code.
Error message if status is false.