Local Time Messages

Delivery

1. Create a template with local_time, mobile_overdue_strategy, mobile_sendout_strategy.
   Use the following JSON payload as example:
   

   {
       "campaign_id": "161156",
       "application_id": "103012",
       "sound": "default",
       "name": "Test name",
       "description": "Test description",
       "type": 5,
       "content_type": 1,
       "push_body": "Test message (body)",
       "mobile_overdue_strategy": 0, // or 1 or 2
    "mobile_sendout_strategy": 1,
       "local_time": "1425130929"
   }

   
   

   Where mobile_overdue_strategy of 0, 1, or 2 signifies now, never, and next day respectively.
   local_time is the UNIX timestamp of the local schedule date. For example, if all devices should receive the message on 2015-11-10 16:00 in their country's time, then the value will be equivalent to MySQL's UNIX_TIMESTAMP('2015-11-10 16:00') which is 1447171200.

2. Trigger the message like a regular template message (such as in direct message). Info available here.

Cancellation

A pending or processing local message can be cancelled using the following API:

Verb

PUT

URI

http://<hostname>/api/v3/message/direct/cancel

Body

{
    "app_id": 1234,
    "message_id": 1234
}