Last Updated: Monday, January 7, 2019
A Broadcast entity is a message template that has been scheduled and/or delivered to Subscribers within the Mobile Database.
The following are the three main sections to a Broadcast:
- The Metadata information, which includes the fields about the Broadcast, such as the ID, URL, created date, and so on.
- The Targeting information, which includes the fields used to identify recipients and craft the message.
- The Delivery information, which is the metadata about the actual message delivery.
The following is the JSON representation of an SMS Broadcast entity within the APIs.
The following is the JSON representation of a Push Broadcast entity within the APIs.
|Max Char Length|
Vibes unique identifier for each Broadcast.
|4 - 9 characters|
The status of the Broadcast. Examples (always lowercase):
|url||String||50||Unique resource URL for the Acquisition Campaign.|
|name||String||The descriptive name of the Broadcast message. Example: "First alert message".|
|created_by||String||The email address of the person who created the Broadcast.|
|The application. Example: null, api.|
|send_scheduled_date||Timestamp||20||The date and time the Broadcast is scheduled to be sent. It should be in the ISO 8601 format - for example: 2017-02-16T17:30:00Z.|
The targeting information for the Broadcast. The message_template is the text for the SMS or push message (with optional custom field or incentive tags).
Examples: message_template, channel, short_url_base, source_short_code, source_lists, shorten_urls.
|delivery||Timestamp, String||The information about the Broadcast delivery, including recipient_count, send_start_date, and enqueue_completed_date.|
|created_at||Timestamp||20||The date this Broadcast was created. It should be in the ISO 8601 format - for example: 2017-04-04T16:06:10Z.|
|updated_at||Timestamp||20||The date this Broadcast was last updated. It should be in the ISO 8601 format - for example: 2019-05-12T05:09:48Z.|