Managing message models
A message belongs to a single campaign. If you want a generic message that is not bound to a specific campaign, you should create a message model.
A message model is reusable and has some advantages over an individual message. See Messages and message models for more details.
Release 220.127.116.11 introduced a number of retrieval elements for message models, which simplify typical automatic use cases. These elements all begin with findMessage.
A message model and the content template that it includes, may result in a large amount of data. Because of this, we provide retrieval model variations that return a message model without the content. These variations all begin with findMessageInfo. We recommend that you use these variations whenever you do not need the content template. The performance of your application will improve as a result, because of less data being transferred during each API call.
Click the appropriate link for more details about the relevant element:
- createMessageModel: Creates a parent message as a model for campaigns from the same sender to the same recipients.
- findMessageModels: Searches for message models.
- findMessageModelsBySubscriberSource: Searches for message models by subscriber source.
- getMessageModelById: Get a single message model by its identifier.
- findMessageByCampaignId: Get a single message model by campaign identifier.
- findMessageInfoByCampaignId: Get a message model by campaign identifier omitting message content.
- findMessages: Searches for message models.
- findMessagesInfo: Searches for message models omitting message.
- findMessagesByCampaignName: Searches for message models by campaign name.
- findMessagesInfoByCampaignName: Searches for message models by campaign name omitting message content.
- findMessagesByChannel: Searches for message models by channel.
- findMessagesInfoByChannel: Searches for message models by channel omitting message content.