Porting Enhancements: GB Partial Port Requirements, Standardized Rejection Codes, and New Port Timeline

We’re rolling out a set of updates designed to make number porting with Telnyx more reliable and transparent. These changes improve data validation for GB local partial ports, standardize rejection handling, and introduce clearer event tracking for every port order.

Greater Accuracy for GB Local Partial Ports

We’ve introduced new requirements to improve accuracy and prevent rejections when processing GB local partial ports. When creating a GB local partial port, you’ll now need to:

• Provide the number ranges that will remain with your current provider.
• Specify whether each range should stay active or be disconnected.
• If the Billing Telephone Number (BTN) is part of the port, all remaining ranges must still be listed, but can only be marked for disconnection.

We’ve also removed the option to assign a new BTN during GB local partial ports, as this is not supported in the GB local porting process. These changes apply only to GB local partial ports. Full ports and other countries remain unaffected.

Why it matters:

Providing complete number range data ensures the losing carrier can validate your order and prevents unnecessary rejections.

For API users:

If you manage porting via API, this new behavior will remain disabled initially. A six-month transition period will precede enforcement, with a mandatory cutover date of April 13, 2026.

Standardized Port-Out Rejection Codes

We’ve standardized rejection handling to reduce confusion and improve automation. Previously, users could type any reason when rejecting a port-out order, including invalid ones, which caused orders to revert to “pending.”

Now, you can query eligible rejection reasons and select from predefined codes. This change: Prevents invalid rejection reasons. Reduces customer confusion. Enables better automation and consistency for Porting Ops.

Explore the rejection codes in our Developer Documentation.

New Port Timeline for Complete Visibility

We’ve added a new “Timeline” tab to the detailed view of every porting order. You can now:

View a full history of porting events, including status updates, comments, and split orders. Rebroadcast webhook or email notifications for specific events, useful for troubleshooting and testing integrations.

Developers can learn more in our Porting Events API documentation.

Why It Matters

These updates make porting more accurate, standardized, and transparent:

• Fewer rejections through better data validation.
• Consistent workflows across porting operations.
• Deeper visibility into each port’s lifecycle.
• Improved automation for integrated systems.

We’re continuously refining porting to deliver a faster, more reliable, and developer-friendly experience across the Telnyx platform, test out our new functionality and share feedback with the team in the Mission Control Portal.