Skip to main content

Release notes

Ahmed Boghdady
Updated

Release notes

Release Features and fixes
December 2025

Zitadel SSO

MO/MT search timeout warning

Self-serve daily MT report generation
November 2025 Mobile API domain update
October 2025 MO and MT searches and export capabilities
April 2025 Improved filtering on the MOs and MTs pages
March 2025 Reset filters
February 2025

CSV export

RCS rich functionality

Unmapped delivery status codes
November 2024 RCS rich cards and carousels
September 2024 Session log out
August 2024 Media files via RCS
July 2024

Broadcast message via RCS

RCS fallback to SMS includes the status code

"Scheduled_at" parameter accepts local time

Suppress RCS failover to SMS
June 2024 Added SMS fallback message copy
May 2024

Mobile API enhancements

Support user MTs and MOs access issue fixed
April 2024

Updated send now broadcast

Errors for invalid mobile directory numbers (MDNs)
February 2024 New retry capabilities for outages
January 2024

Brand search error fixed

Programs activate / deactivate button error fixed

Mobile API (US and UK) enhancements

Mobile API (UK only) enhancements
December 2023

Validation error message fixed

Mobile API (US only) enhancements

Mobile API (US and UK) enhancements

Expanded region support
October 2023

API key/secret

Encoded identifiers

September 2023

503 error code

Access to keyword phrases

Updated Billing report
June 2023 New Help Center

 

December 2025

Zitadel Single Sign-on (SSO)

Zitadel SSO is an enhanced security update to enable multi-factor authentication on the Mobile API platform. Active users of the Mobile API platform will receive an email from Zitadel with an invite link prompting to set up their multi-factor authentication and platform sign-on with Zitadel.

MO/MT search timeout warning

Mobile API now displays an informative warning when message searches exceed expected response times, helping users understand when to narrow their search parameters.

Self-serve daily MT report generation

Customers can now generate on-demand daily MT (mobile-terminated message) reports for any single day directly from the Mobile API platform, providing secure self-service access to daily traffic data.

 

November 2025

Mobile API domain update

All domain URLs in the Mobile API have been updated to the new "Mobile Commons" domain. This update ensures a smooth transition to the new domain without impacting your existing integrations or API functionality.

Region Old New
EU mobileapiuk.uplandsoftware.com eu-api.mobilecommons.com
US mobileapi.uplandsoftware.com us-api.mobilecommons.com

 

October 2025

MO and MT - Expanded Search and Export capabilities

MO and MT searches and exports can now return the full result set, removing the previous 100-record limit.

 

April 2025

Improved the filtering experience on the MOs and MTs pages

  • The browser location path/parameters now updates to reflect the applied filter inputs.

  • When loading these pages, filters are automatically applied based on the corresponding URL parameters.

  • Emails delivering CSV exports now include a link to the page with the exact search parameters used for the export, making it easier to revisit and analyze filtered data.

 

March 2025

Reset filters

Added the Reset Filters button to the MOs and MTs search pages, allowing users to reset all search fields at once.

 

February 2025

The release includes the following updates:

  • You can now export a CSV from both the MT and MO pages in the Admin UI.

  • RCS rich functionality has been added to Swagger.

  • System updated to handle all unmapped delivery status codes.

 

November 2024

RCS rich cards and carousels

Mobile API now supports RCS standalone rich cards and carousels.

 

September 2024

Session log out

To enhance security, a session will now log out after 10 minutes of inactivity.

 

August 2024

Media files via RCS

Mobile API now supports sending media files via RCS.

 

July 2024

New features

The following enhancements were made to Mobile API:

  • A broadcast message can now be sent via RCS.

  • RCS fallback to SMS will include the status code in the DLR webhook.

  • The "scheduled_at" parameter can now accept local time with timezone according to ISO-8601 standards.

  • You will now have the option to suppress RCS failover to SMS.

 

June 2024

Added SMS fallback message copy

SMS fallback message copy has been added to the DLR Webhook for RCS. If you have any questions about our RCS functionality, please reach out to your account manager.

 

May 2024

Resolved issue

Resolved a bug that prevented a support user from being able to access mobile-terminated messages (MTs) and mobile-originated messages (MOs).

 

New features

The following enhancements were made for Mobile API:

  • Released RCS functionality, including:

    • Ability to send text via RCS with a character limit of 160 or higher.

    • Webhooks to allow customers to receive MOs, MTs, Delivery Receipts, and Read Receipts.

    • Provisioning of an RCS Agent.

More information and details about RCS functionality will be available soon. If you have any questions in the meantime, you can contact your account manager.

 

April 2024

Updated send now broadcast

The send now broadcast has been updated so that if a broadcast is triggered more than three hours past its intended scheduled time, it will not be sent. This will prevent the propagation of delayed broadcast executions into very delayed sends.

Errors for invalid mobile directory numbers (MDNs)

Errors for invalid MDNs for the inline broadcast will be returned, regardless of the overall broadcast success. Records will not be generated for these invalid numbers.

 

February 2024

New retry capabilities for outages

Mobile API has implemented retry capabilities to handle momentary outages on the customer's service.

 

January 2024

Resolved Issues

  • Resolved a bug that prevented users from searching for brands by list of profile URL.

  • Resolved a bug that prevented users from using the programs activate / deactivate button on the Admin panel.

 

New features (US and UK)

The following enhancements were made to Mobile API for US and UK users:

  • "Scheduled_at" has been put behind a feature flag. This means that the ability to use "scheduled_at" to schedule either past or current messages can only be done if the feature flag is enabled. Users will have to contact their account manager to receive access to this feature. See Sending mobile-terminated messages (MTs) for more information on "scheduled_at".

  • Users will now receive a 102 error for invalid MDNs (mobile directory numbers) in unsupported regions.

  • Company users now have the ability to generate an API key/secret from the Admin panel.

  • Company administrators can now generate an API key/secret from the Admin panel.

  • DLRs (delivery receipts) will now return the time rounded to seconds for the "notified_at" field.

 

New features (UK only)

The following enhancements were made to Mobile API for UK users only:

  • Mobile API can now handle MDNs in UK localization format. For example, the following can now be handled:

    • Country code present and no leading zeros

    • Country code present and one leading zero

    • Country code absent and one leading zero

    • Country code absent and no leading zeros

    • Country code absent and two leading zeros

    • Country code present and two leading zeros

  • Mobile API has enabled "auto_enroll" feature flag for Send Message and Scheduled Send Message for brands (alphanumeric sender ID). See Sending broadcast messages for more information on "auto_enroll".

  • A longcode or a shortcode can now be associated to an alphanumeric sender ID in order to support opt-in compliance.

  • International support for Mobile API has been expanded to the several regions. Please see the Country support page for a full list of countries you can send messages to.

 

December 2023

Validation error message fixed

To address an issue where the scheduled_at parameter in inline broadcast programs endpoint was giving an internal server error, a more descriptive validation error is now provided, following the standard error schema for Mobile API.

Mobile API (US only)

The following enhancements were made for Mobile API (US) only:

  • Broadcast and sendnow APIs are restricted to only one image attachment per MT.

  • To support delivery of MMS messages, this release adds MMS failover to SMS capabilities.

  • A new Webhook functionality allows customers to receive a notification when their uploaded media attachment has been resized and is available for use.

Mobile API (US and UK)

  • To help customers remember their key, we've added an API Key/Secret description field to the Admin panel. The contents of the description field will also be available in the client’s billing report.

  • A Company Admin user can generate new key/secrets for their company.

  • To support Automate users moving to Mobile API, the scheduled_at option now supports dates in the past.

Expanded region support

Region support has been extended to the following countries:

  • Albania

  • Algeria

  • Andorra

  • Angola

  • Austria

  • Brazil

  • Bulgaria

  • Canary Islands

  • Croatia

  • Czech Republic

  • Estonia

  • Faroe Islands

  • Finland

  • Greenland

  • Guadalupe

  • Guam

  • Guatemala

  • Iceland

  • Latvia

  • Lebanon

  • Lichtenstein

  • Lithuania

  • Luxembourg

  • Malta

  • Martinique

  • Mauritania

  • Mauritius

  • Monaco

  • Pakistan

  • Puerto Rico

  • Reunion Island

  • Russia

  • Serbia

  • Seychelles

  • Slovenia

  • Taiwan

  • Ukraine

  • Zambia

For a complete list of countries supported, including their country codes, see Country support.

October 2023

API key/secret

API key/secret will now be hashed after it is created. The user will have to store the key/secret immediately after creating it. If the user loses the key/secret, they will have to create a new one.

Encoded identifiers

Encoded identifiers have been added to error responses.

September 2023

503 error code

In order to provide more clarity to our customers when the error they’re seeing is only temporary, we are now sending a 503 error code for database connection issues with the Send Message API. The following message will be shared back: “Unable to process request. Please retry at a later time.”

Access to keyword phrases

Users can now access the keyword phrases associated with their programs in the Admin Panel. This will provide full visibility into the programs that they have set up on Mobile API.

Updated Billing report

The Billing report has been updated to include both subaccount and user (name or key id), so that users know who sent out the MTs that they are being billed for.

June 2023

New Help Center

In this release, we introduce a new Help Center for Mobile API docs, which provides key information for building mobile-messaging applications using Mobile API.

Note: See your customer success manager for access to the Help Center.