Explore this week’s updates and releases! 🔎

Browser SDK v4 Release Candidate Now Available
Version 4.0.0-rc.0 of the SignalWire Browser SDK is now available as a release candidate. We're inviting customers to test it and share feedback ahead of the stable release.

Try it out and let us know what you find.

• 📖 Documentation

• 📦 npm

• 💻 GitHub

Pass Custom Variables on Call and Message Creation
You can now include custom_variables when creating outbound calls or messages via the REST API, making that data available to your SWML app during execution or in your status callbacks.

This makes it easier to associate your own context, such as customer IDs, session data, or workflow identifiers, with a call or message and carry it through to later lifecycle events.

• 📖 custom_variables for calls

• 📖 custom_variables for messages

🛠 Bug Fix
Inbound Calls and Faxes to Unconfigured Numbers Now Show in Logs
Inbound calls and faxes to phone numbers without a configured handler will now appear in your logs with a clear error, rather than failing silently. This makes it significantly easier to identify and resolve misconfigured numbers.

Explore this week’s updates and releases! 🔎

SWML Code Editor Now Supports Messaging Scripts

The SWML code editor in the new dashboard now provides autocomplete, suggestions, and schema validation for Messaging SWML scripts, matching the support already available for Voice scripts.

The editor automatically applies the correct schema based on your script type. If your script appears to be the wrong type, the editor will flag it and offer a one-click option to switch, making it easier to catch mismatches before they cause issues in production.

This is available on the new dashboard only.

Custom SIP Headers Now Supported in REST API Call Creation

You can now pass custom SIP headers when creating outbound calls through the REST API, giving you greater control over SIP-level metadata for routing, tracing, and downstream system integration. This brings the REST API in line with the existing connect.headers support already available in SWML. Full documentation coming soon.

📖 REST API Docs

Explore this week’s updates and releases! 🔎

Introducing Inbound Messaging with SWML

You can now assign SWML Scripts and Webhooks to phone numbers to handle inbound messages, bringing the same powerful scripting control you already use for voice to messaging.

Configure routing, conditional logic, and replies directly in SWML. This goes well beyond basic auto-reply, supporting inline switching on message content, variable expansion, HTTP requests, and multi-section documents with full control flow.

To get started, navigate to Phone Numbers in the dashboard, select a number, and assign a SWML Script or Webhook under Inbound Message Settings. You can also assign handlers via the REST API.

This is available on the new dashboard and REST API. If you're on the legacy dashboard, reach out to Support or Sales to get access.

• 📖 SWML Messaging Reference

• 📖 Create a SWML Script

• 📖 Create a SWML Webhook

• 📖 Assign a Resource to a Phone Number

Improved Error Codes for Undelivered MMS

A previously misclassified MMS error code has been corrected. Certain MMS delivery failures that were reported as unknown_destination_handset / 30005 will now appear as mms_expired_rejected_failed_or_unsupported / 30011, more accurately reflecting the type of failure that occurred.

AI Agents Page Performance Improved

Spaces with large numbers of AI Agents sometimes experienced errors and timeouts when loading the AI Agents list. This has been resolved and the page now loads quickly regardless of how many agents are configured.

Explore this week’s updates and releases! 🔎

REST API for Messaging Now Fully Documented

The SignalWire Messaging REST API is now fully documented and ready to use, giving you a direct, programmatic way to send messages, manage compliance, and monitor delivery all from a single API.

The documentation covers three key areas:

• Send a Message: Create and queue outbound SMS or MMS messages. The API automatically determines message type based on the presence of media or the send_as_mms flag. Supports status callbacks, so your system can receive real-time delivery updates.

• Redact a Message: Clear the body of a previously sent message for compliance or privacy purposes. Works on messages in terminal states (delivered, undelivered, or failed).

• Message Status Callback: Receive a webhook payload each time a message transitions to a new delivery state. The same payload shape is used across the REST API, Relay SDK, and SWML send_sms callbacks, keeping your integration consistent regardless of how you send messages.

Explore this week’s updates and releases! 🔎

Error Details Now Visible in Message Logs

Message logs now display error codes and error messages directly in the UI, giving you full visibility into failed messages without needing to make a separate API call.

Previously, this information was only accessible via the API. Now, if either value is present, you can see it at a glance in the dashboard — making it faster to diagnose delivery issues without needing to make a separate API call.

Scripts Filter Split into SWML and CXML

The Resources UI filter for Scripts has been separated into two distinct filters: SWML and CXML.

This makes it easier to find and manage your scripts by type without sorting through a combined list.

Flexible Codec Format Support for Dial Requests

You can now pass codecs as either an array of strings or a comma-separated string when making a calling/calls dial request, giving you greater flexibility in how you configure your calls.

Supported codecs include: PCMU, PCMA, OPUS, G729, G722, VP8, and H264.

📖 See the full codecs parameter documentation for details.

Explore this weeks updates and releases! 🔎

Hold Music URL on SIP Endpoints

Physical SIP phones can now have a set hold music URL that will be played when hold is pressed on an outbound or inbound call to that SIP endpoint.

Explore this weeks updates and releases! 🔎

Conference Audience Feature Deprecation

The Conference Audience feature has been deprecated and removed as part of ongoing platform modernization efforts.

This change supports improvements to platform stability and enables new regional infrastructure.

Removal of Dashboard Info Panel

The Home Dashboard has a new look! To improve navigation, usability and access to resources the expandable info panel has been removed and you will now see a cleaner, text-based dashboard.

• New dedicated links for Changelog, Support, Docs, and Community resources can be found in the top right menu, Including direct access to the Status page and Documentation links ( that now open in a new window for easier reference)

⚠️ Shutdown of Bahrain RTC POP

The Bahrain RTC POP will be retired on March 27, 2026.

• Calls will automatically route to the next closest available node. No action needs to be taken at this time.

• Any active calls on this node will continue until completion.

Introducing a new Voice Analytics Dashboard, giving you a high-level view of voice call health across your project.

This new dashboard makes it easier to identify potential issues, monitor performance trends, and understand overall voice health — all without needing to build custom observability workflows.

Where to find the new dashboard.

The Voice Analytics Dashboard is now available. Navigate to “Analytics” from the left hand menu →  select the submenu “Voice”.

We want your feedback!

Once you have had time to use the new dashboard, we would love to hear your feedback! Take the Voice Analytics Dashboard Feedback Survey.

Explore this weeks updates and releases! 🔎

✨ Code Editor Toolbar Improvements

The code editor toolbar has been enhanced for easier script management.
You can now copy scripts directly from the toolbar, and read-only editors still provide access to tools like copy and resize.

🧪 New “Click to Test” Button

You can now test resources directly from the browser.
A new Click to Test button on the Resource detail screen lets you initiate a test call without assigning a handler or using an external phone.