...
Name | Type | Example | Description | ||
---|---|---|---|---|---|
id | String |
| Unique message ID. You can use the id from provider | ||
provider | String |
| Name of the messaging provider used in lowercase Current known providers:
| ||
message_created_at | String |
| Datetime the message was created by you in ISO 8601 format. If none is given, this will be the time the message is processed. | ||
message_sent_at | String |
| Datetime the message was sent (to or from the carrier) by your provider (CPaaS) in ISO 8601 format. If none is given, this will be the time the message is processed. | ||
message_finalized_at | String |
| Datetime the message was marked finalized by the provider (CPaaS) in ISO 8601 format. If none is given, this will be the time the message is processed. | ||
error_code | String |
| Code the provider returned if there was an issue with sending this message | ||
from_number | String |
| Phone number formatted in E.164 the message is being sent from | ||
to_number | String |
| Phone number formatted in E.164 the message was sent to | ||
body | String |
| Contents of the message sent | ||
status | String |
| Status returned from the provider | ||
direction | String |
| Direction of the message. Certain providers have more than inbound/outbound descriptions. These will be saved for future reference, but also normalized into inbound/outbound buckets | ||
message_type | String |
| Kind of message sent: SMS/MMS | ||
segment_count | Integer |
| Number of segments provider broke message into for sending |
...