Best practices for Message Center message removal

This best practices guide is designed to outline some steps that can be taken to ensure your Message Center messages display as expected, are removed from devices automatically once they are no longer applicable, and gives you access to the necessary information for a manual message removal.

Testing on a device

Testing on a device can be helpful in avoiding typos, ensuring the message displays as expected, and confirming links are properly configured prior to the message reaching your audience. When removing a Message Center message, a test device can be used to confirm a successful removal. See our documentation on Test Devices for more information on identifying and setting up your devices.

Using an expiry

For time-sensitive messages include an expiry time, which automatically removes messages from user's inbox at the specified time. This is useful in case an error was made or anything that renders an existing message obsolete or inaccurate. Below is an example of a Message Center message that pushes to local time and includes an expiry.

         "alert":"Taco Tuesday"
         "title":"Taco Tuesday",
         "body": "<html><h1>Let's Eat!</h1></html>",


Logging all API requests and responses

Please log your full API requests and our API responses to you. The response includes both the Push ID and Message ID which are necessary for Message Center message removal. Below is an example of a standard response.

    "ok": true,
    "operation_id": "fe60a5e1-b4a0-49e3-b6b3-97649d39e88f",
    "push_ids": [
    "message_ids": [
    "content_urls": []


For messages that push to local time, a Push ID is assigned to each time zone. This means that for each push to local time message there can be up to 42 Push IDs. To remove a local delivery message the Push ID for each time zone is required. Below is an example of a response for a push to local time message.


    "ok": true,
    "operation_id": "b7e227d3-e0d8-4f18-844e-1e66531f9b07",
    "schedule_urls": [
    "schedule_ids": [
    "schedules": [
            "url": "",
            "schedule": {
                "local_scheduled_time": "2017-01-15T12:00:00"
            "push": {
                "audience": "all",
                "device_types": [
                "notification": {
                    "alert": "Taco Tuesday"
                "message": {
                    "title": "Taco Tuesday",
                    "body": "<html><h1>Let's Eat!</h1></html>",
                    "content_type": "text/html",
                    "content_encoding": "utf-8",
                    "expiry": "2017-01-27T12:00:00"
            "push_ids": [

The Push IDs for local delivery messages created via the Go Dashboard can be retrieved via the Schedules API prior to the message being sent. Read our documentation on Schedules.

Related Content:

Was this article helpful?
0 out of 0 found this helpful
Submit a request