We’ve updated the Applications page to now support the ability to send messaging events to separate endpoints. One for inbound messages and another for status (outbound) messages.

With this update you can:

• Configure separate callback URLs for inbound messages and status (outbound) callback events
• Set status (outbound) callback as optional
• Select which status (outbound) callback events you receive

Existing applications will continue to work as they currently do. If you’d like to take advantage of these Messaging Callback configuration options, visit the Applications page in the Bandwidth Dashboard to update.

You can now access real-time message data in the Bandwidth Dashboard under the Insights Tab or via the Get Messages API! This tool allows you to search and investigate the real-time status of your message logs. Use Messaging Insights for monitoring, testing, and troubleshooting the performance of your messages. You can find and filter messages by:

• Message ID
• Date
• Status
• Error Code
• To and/or From Number, and more!

We enabled all administrators and non-administrators who have the Reporting role. If you’re an administrator, you can grant users access by enabling the Messaging Insights role on their user profile.

We have launched an updated version of the Bandwidth Dashboard UI. The new experience offers streamlined user workflows, consistent terminology, easier scrolling and navigation, and improved accessibility.

We’ve added new fields to our Message Detail Records! You can now find Carrier Name (for instance, “Verizon”, “AT&T”, “T-Mobile”, “Sprint”) and Location ID (the Location field represented in the Bandwidth Dashboard) in your Message Detail Records (MDRs).

These fields provide more detail to understand which carrier the message was sent to and which of your locations the message was associated with so you have better insight into your messaging traffic.

Bandwidth now supports Delivery Receipts (DLRs) on MMS and group messages. With this update customers can enjoy a more complete view of their messaging delivery success.

Learn more about this change:

MM4 Users:

• Error codes
• MMS Delivery Receipts

V2 API Users:

• Error codes
• MMS Delivery Receipts

Customers can now use an HTTP Get API endpoint to search for individual messages and their statuses. This allows you to proactively check on message delivery status at any point after messages are sent. Get started by checking out our developer documentation.

Hosted Messaging gives you the ability to power voice and messaging services separately with the same phone number. This functionality is now available for any phone number via the Bandwidth Dashboard or API. With this improvement your end users can select the voice and messaging service providers that best meet their needs for any given phone number.

Customers can now access Verizon’s 10DLC A2P messaging route via the Bandwidth Local A2P API. This route enables reliable messaging deliverability on local numbers—the first route of its kind. To get started, talk to your client development manager or access our developer documentation.