What's New

Sole proprietors can now resend a brand verification code using POST /accounts/{account_id}/brand_verification_messages. See the Resend Brand Verification Message endpoint in the API documentation for more information.

API authentication now uses a short-lived cache and batches API-key activity updates, reducing database work on each request. Last-used timestamps may take a few minutes to update, but this should provide lower latency and better reliability for our API.

We redesigned the notification email templates with the updated brand, typography, and visual system.

Sole proprietor brand verification texts now use the platform name for white-label projects instead of identifying every registration as Surge.

SIP trunk private beta projects can now list, view, create, edit, and delete SIP trunks directly in HQ.

The campaign registration form now collects the business’s brand name separately from its account and legal business names.

New webhook events are now prioritized over retries, preventing failing endpoints and retry backlogs from delaying deliveries to healthy endpoints.

Surge now prevents messages from being sent through released phone numbers. The embedded composer is also disabled when its sender is no longer active.

You can now browse available US and Canadian phone number inventory, retrieve an individual phone number, and purchase a specific number through the API. See the API documentation for more information:

• List available numbers
• Purchase phone number

Call detail pages now resolve call-leg participants into contacts, Surge phone numbers, and users, with clearer labels and links to related records.

Phone number API responses and phone-number webhook payloads now include a campaign object with the campaign ID and current attachment status. The existing campaign_id field is deprecated.

Verification destination rate limits are now scoped to each project, preventing activity in one project from consuming another project’s allowance for the same destination.

voicemail.received, call.ended, and recording.completed webhook events now include the Surge phone number ID along with the to and from numbers. See the documentation for more information:

• Voicemail received event
• Call ended event
• Recording completed event

Fixed an issue that could prevent customers from seeing their previous conversations in the embedded support chat.

Fixed a race condition that could return a 422 when multiple messages were sent simultaneously to the same new contact or conversation.

Creating a campaign with a TCR ID that is already linked now returns 409 Conflict instead of a generic validation response.

Webhook event history queries were optimized to improve page load times, especially while the database is under heavier load.

You can now pass a settings object when creating a message to override account-level settings for that message. Currently, settings.link_shortening supports "enabled" and "disabled".

We redesigned the login, registration, email confirmation, forgot password, and reset password pages with the updated Surge visual design system. More of HQ to come!

SIP trunk private beta projects can now list, retrieve, update, and delete SIP trunks through the API, in addition to creating them.

HQ now has call list and call detail pages, including call direction, status, duration, contact, phone number, and call leg details.

Phone number call handling can now use audio files for voicemail greetings.

Fixed an issue where monthly campaign fees could be counted once per campaign submission instead of once per campaign.

Message senders are now easier to identify in the inbox and embedded conversation views.

Fixed an issue where request and response bodies could disappear from API logs when filtering.