The Message object
A Message Detail Record (MDR) is generated for every message sent or received by Plivo.
An MDR object has these attributes.
Attributes
message_uuid string | A 36-character string that uniquely identifies a message detail record. |
message_time string | The exact timestamp at which an outbound message was initiated or an inbound message was received. |
message_direction string | Indicates the direction of the message. It is set to |
message_state string | Indicates the current status of the message. Outbound messages may be in any of the following states: All outbound messages are initially Inbound messages may be in any of the following states: All inbound messages are initially marked as |
message_type string | Set to |
from_number string | Identifies the source address of the message. For For |
conversation_id string | WhatsApp-only attribute. Represents the ID of the conversation to which the given message belongs. |
conversation_origin string | WhatsApp-only attribute. Possible values: Describes how a WhatsApp conversation was initiated.
|
conversation_expiry_timestampstring | WhatsApp-only attribute. Unix timestamp applies when the current conversation expires. This is 24 hours after the conversation started. A conversation is considered started when you send the first outbound message. |
to_number string | The destination phone number to which the message was sent. For inbound messages, this is the Plivo phone number on which the message was received. |
destination_country_iso2 string | The ISO2 code of the country associated with the destination number. |
units integer | Indicates the number of units that a message was split into. |
total_rate string | The charge applicable per unit of the message. |
total_amount string | The total amount charged for this message. Typically, this is equal to the product of total_rate and units . |
requester_ip string | The IP address from which the message request originated. We recommend you monitor this field to identify possible account misuse and authentication credential takeovers. |
error_code string | The Plivo SMS error code that helps identify the cause for a message delivery failure. For successfully delivered messages, this attribute is set to |
tendlc_registration_status string | Indicates nature of 10DLC registration for that message. Relevant only for long code messaging in the US. |
tendlc_campaign_id string | The campaign ID associated with the message. Relevant only for long code messaging in the US. |
replaced_senderstring | Sender ID (numeric or alphanumeric) that left Plivo’s system. In some instances, Plivo replaces the sender to ensure compliance and deliverability. |
is_domesticboolean | Indicates whether a message is treated as domestic. Relevant only for long code messaging in India; supports India-specific use cases such as DLT messaging and India DND filtering. The value of the field is derived from the way the organization classifies the sender ID at registration. |
dlt_entity_idstring | The DLT entity ID passed in the message request. Relevant only for DLT-eligible India customers. |
dlt_template_idstring | The DLT template ID passed in the message request. Relevant only for DLT-eligible India customers. |
dlt_template_category string | The template categorization registered in DLT portal. Relevant only for DLT-eligible India customers. Allowed values: transactional , promotional , service_implicit , service_explicit |
destination_network string | Indicates the carrier network for the recipient number you are sending messages to. |
carrier_fees_rate string | The carrier surcharge fee applicable per unit of the message. |
carrier_fees string | The total carrier surcharge fee charged for this message. Typically, this is equal to the product of carrier_fees_rate and units . |
log string | For outbound messages, the data logging preferences were set in the message request. For inbound messages, preferences were set during the application setup as shown here. Possible values: If set to If set to If set to |