What's New

Projects can now disable public attachment access and require authenticated access for attachment files. This goes hand in hand with our get attachment file endpoint that we shipped last week.

API logs can now be filtered by success or failed status, making it easier to investigate request history.

Queries for our embedded inbox component were optimized, resulting in a 68% reduction in average load time. You should now see much faster page loads and updates.

Saved usage reports now use the pricing plan that was active during the report period instead of always showing current pricing. This should make historical usage reports more accurate.

Phone numbers can now be named, and the name will be visible across the UI, API, and webhook payloads. See the purchase phone number endpoint in the documentation for more details.

While we've had multi-factor auth as an option for a long time, we now have the ability to enforce MFA in projects. If you would like to require MFA for all members of your project, please reach out to support.

A new authenticated API endpoint is available for retrieving attachment files, providing a more secure alternative to public attachment URLs. See the get attachment file endpoint in our documentation for more details.

Surge can now automatically warn and log users out after 15 minutes of inactivity for stronger account security. Please reach out to support if you would like to have this enabled for your account.

link.followed webhook events now include the full message object instead of only a message ID. This means any metadata stored on the message, along with all other message details, will be present on those webhook events to make it easier for you to track conversion for your messages and blasts.

Projects can now manage multiple named AI agent API keys and choose which key to use when configuring a phone number integration. This allows you to set up multiple AI agent platforms within your project or even within the same account.

Surge now tracks permanently undeliverable destinations and blocks future sends to numbers that are known to fail, with sender-type-specific handling for local, toll-free, and short code traffic. This should save you money as you will no longer be charged for those messages.

Inbound MMS attachments with unrecognized MIME types no longer fail during ingestion. Surge now stores them without guessing a file extension.

Campaigns created through the API can now be updated with a new PATCH /campaigns/{campaign_id} endpoint. See the update campaign endpoint in the documentation for more details.

The API now supports creating audiences and adding contacts to audiences, making audience management available without using the UI. See the create audience and add contact to audience endpoints in the docs for more details.

When sending a Blast through our API, it was already possible to provide the phone number from which the Blast should be sent. HQ didn't previously support that feature though, so we've now added a dropdown so that you can select which phone number should send the Blast when sending through our UI.

We've now added Retell as a supported AI agent platform for Voice. On the phone number settings page, you can select to have inbound calls handled by an AI agent, then select Retell as your platform of choice. By providing your Retell API key, we will import your Surge phone number into Retell for you so that your Retell agent can make and receive calls using your Surge phone number.

For phone calls through the ElevenLabs agent platform, we had some issues where calls were cut short when we deployed a change to our servers. That has now been fixed, so ElevenLabs agent calls should now be more reliable.

While Canadian accounts could previously be created manually through HQ, we've now added the ability to create Canadian accounts through the API as well.

Accounts in Canada will need to have a valid Canadian Business Number instead of an EIN. You can validate the business number beforehand using Canada's Business Registries and Federal Corporation Search. If the business was registered provincially or doesn't appear in either of the registries, a special registration process will be needed which requires additional fees. Reach out to support for more information.

We've updated the embedded components to use message clustering similar to the way iMessage does it. Messages sent within a minute of each other will be grouped together with less spacing than normal, and messages sent within an hour of each other will be grouped under a date/time header. This helps to declutter the conversation view and provide a more familiar interface for customers.

Right now this new functionality is disabled by default. If you would like it enabled for your project, please reach out to support. Once we've tested it thoroughly, we will enable it for all projects.

For users in our private beta for recording calls, you now have the ability to always record outbound calls as well as inbound calls. In the phone number settings, you will see a new "Record outbound calls" checkbox right below the "Record inbound calls" checkbox.

Currently this functionality can only be enabled or disabled for all calls. We have no way to override it on a specific call yet.

We have added an endpoint for listing all of the users in an account. See the documentation for the list users endpoint for more information.

When an area code was provided to the API for purchasing a phone number, and that area code is associated with a country or territory outside the US (like the 345 area code for the Cayman Islands), our system was returning an unknown error. We will now handle that properly and return an error explaining that the area code is not valid.

For projects in the beta for our embeddable softphone, you can now route inbound calls to a list of multiple users instead of just a single user. When you do this, all users' softphones will ring simultaneously, and the first user to answer the call will receive it.

We've added new endpoints for getting a recording or listing all the recordings in an account. This will be especially helpful for making sure that you've deleted all recordings if you don't want to pay Surge to store them for you. See the documentation for the get recording endpoint and list recordings endpoint for more information.

Some code paths for creating a message weren't saving message metadata properly, and the metadata wasn't being returned in the API responses. This has been fixed so that message metadata will now work as expected.