Updates to the MoveTns Order API

What's happening?

Effective August 1, 2025, we’re updating the MoveTns Order API to enhance the overall order experience and reduce the risk of service disruptions when moving phone numbers.

What do I need to know?

These updates will introduce the following improvements:

Graceful handling of invalid numbers: Today, if the MoveTns Order API request includes numbers not owned by the source account (e.g., from another of your accounts), it will fail, requiring you to identify and remove the invalid numbers manually. Starting August 1, instead of failing the entire order, it will skip the invalid numbers and proceed only with the valid ones. The order status will be “partial”, and a warning will be provided in the response identifying which numbers were invalid and skipped.

Protection for messaging services and 10DLC campaigns: Today, if you move a messaging-enabled number assigned to a 10DLC campaign to an incompatible Account or Location, it will be removed from that campaign. Starting August 1, such moves will be blocked by default to protect critical messaging functionality, and you’ll receive an error explaining the issue with the affected numbers.

What do I need to do?

Please review the updated MoveTns Order documentation and do the following:

Simplify error handling for invalid numbers: If you currently monitor the MoveTns Order requests for failures due to invalid numbers, you may be able to simplify your process. The order will now submit, and you can monitor the response for any “invalid number” warnings without having to resubmit the valid numbers.

Preserve or remove messaging intentionally: If you want to move numbers in a way that removes messaging services or 10DLC campaign associations, you’ll need to include the appropriate new parameters in your request. Without them, the system will block the move to preserve these services by default.

Questions?

Please open a ticket with your Bandwidth Support Team or call us at (855) 864-7776!