...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
Delivery
- Create a template message with
schedule_type = 1andschedule_datecontaining the schedule date in UNIX timestamp formatwithlocal_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": 10, // or 21 or 32
"mobileschedule_sendout_strategytype": 1, // or 24 for orbest 3time
"localschedule_timedate": "1425130929"
}overdue- the overdue policy that will be applied to the message.0for now,1for never, and2for next day.schedule_type- the sendout strategy that will be used.1signifies 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.
- If this is a Local Time message, trigger the message at UTC-16
- If this is a Best Time message, trigger the message at 09:00 UTC at the day before the
schedule_date
Value mapping
Overdue strategy
strategy | code |
|---|---|
| now | 0 |
| never | 1 |
| next day | 2 |
Schedule type
| strategy | code |
|---|---|
| now | 0 |
local | 1 |
| BTTS schedule | 4 |
Cancellation
A pending or processing local message can be cancelled using the following API:
Verb
| Code Block | ||
|---|---|---|
| ||
PUT |
URI
| Code Block | ||
|---|---|---|
| ||
http://<hostname>/api/v3v4/message/direct/cancel |
Body
| Code Block | ||
|---|---|---|
| ||
{
"app_id": 1234,
"message_id": 1234
} |