Delivery
- 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
"mobileschedule_
sendout_strategytype
": 1,
"localschedule_timedate": "1425130929"
}Where
mobile_overdue_strategy
of 0, 1, or 2 signifies now, never, and next day respectively.local_time
isoverdue
- the overdue policy that will be applied to the message.0
for now,1
for never, and2
for next day.schedule_type
- the sendout strategy that will be used.1
signifies local time, which is the only relevant value for this flowschedule_date
- 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'sUNIX_TIMESTAMP('2015-11-10 16:00')
which is 1447171200. - Trigger the message like a regular template message (such as in direct message). Info available here.
...
strategy | code |
---|---|
now | 0 |
never | 1 |
next day | 2 |
...
Schedule type
strategy | code |
---|---|
now | 0 |
local | 1 |
BTTS schedule | 4 |
...