What's New

Projects in our SIP trunking private beta can now create their own SIP trunks through the API. SIP trunks support both IP-based and credential-based authentication, and once created you can attach a phone number to a SIP trunk as a call handling method.

Previously, if you submitted a campaign to us through either the API or HQ, we would charge you for it. Now we will only bill you for the campaigns that are sent through to the carriers.

We've added optional monthly message limits that cap the number of outbound messages a project can send each month based on its subscription plan. These limits are high enough that most accounts will never see them, but they will prevent unintentional runaway spend or abuse. If you'd like to have the limit lifted for your account, please reach out to support.

You can now release a phone number through the API with the new DELETE /phone_numbers/{phone_number_id} endpoint. See the release phone number endpoint in the documentation for more details.

Fixed an issue where re-purchasing or re-adding a phone number that had previously been released could cause conflicts between the released and active versions of the number.

We've added new API endpoints to streamline onboarding for AI agent platforms. POST /agents/v0/projects provisions a passwordless user, platform, account, and API key in a single call, along with a demo phone verification, and POST /agents/v0/phone_verifications/{verification_id}/checks confirms the SMS verification code to finish setting up a demo participant. See our new skills file for instructions.

Following our undeliverable number detection, projects can now choose to bypass the undeliverable-number check. This is useful if you'd rather attempt delivery to numbers that have previously failed than risk blocking a message that might still get through. Reach out to support to enable this for your project.

In order to prevent abuse through demo numbers, Surge now prepends [SURGE DEMO] at the beginning of any messages sent through the demo number. This way recipients will be able to see that it's a demo message, and demo numbers can't be used for smishing attacks.

We added a new endpoint for listing all of the accounts in your project. See the documentation for the list accounts endpoint for more details.

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.