Additional Steps on a Porting Order

After creating a porting order, you may need to complete additional steps before submission, depending on the values you entered.

You can check whether there are any additional steps by reviewing the additional_steps array before you submit the order.

• "additional_steps": [] - there are no further actions. You are cleared to proceed.
• "additional_steps": ["{some value}"] - there are additional steps you need to take before you will be allowed to submit your porting order.

A sample request is shown below (most of the response is omitted to highlight the additional_steps array):

curl --location --request GET 'https://api.telnyx.com/v2/porting_orders/072df5c8-567a-4bf0-a46f-46bbbac65fe5' \
--header 'Authorization: Bearer YOUR_API_KEY'

Response:

{
    "data": {
        "id": "072df5c8-567a-4bf0-a46f-46bbbac65fe5",
        "status": {
            "value": "draft",
            "details": []
        },
…
        "additional_steps": [
            "associated_phone_numbers"
        ],
…
   }
}

This guide will walk through those various additional steps cases, and how to tackle them.

When filling out the porting order:

• The order is for GB local phone numbers
• You indicated that it would be a partial_port

For partial porting GB local phone numbers, we need to know all phone numbers associated with your account, including those that are remaining with the losing carrier. For the phone numbers remaining with the losing carrier, we also need to know whether you intend to keep or activate each of those phone numbers. Without this information, we cannot process your porting order (it will be rejected by the losing carrier).

For the phone numbers on your account with the losing carrier that are not porting to Telnyx, you need to indicate:

• Which phone numbers you would like to remain active with the losing carrier after the port completes.
• Which phone numbers can be disconnected after the port completes.

To do this, you can use the POST v2/porting_orders/:porting_order_id/associated_phone_numbers endpoint (API reference here). With this endpoint, you can specify ranges of phone numbers and whether the range should remain active (keep) or should be disconnected (disconnect). An example request is shown below:

curl --location --request POST 'https://api.telnyx.com/v2/porting_orders/072df5c8-567a-4bf0-a46f-46bbbac65fe5/associated_phone_numbers' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer YOUR_API_KEY' \
--data '{
    "phone_number_range": {
        "start_at": "+441709241253",
        "end_at": "+441709241259"
    },
    "action": "keep"
}'

Response:

{
    "data": {
        "id": "a896d22e-60a3-4006-ae12-dea15abe7efa",
        "record_type": "porting_associated_phone_number",
        "action": "keep",
        "updated_at": "2025-10-09T20:31:48.518554Z",
        "country_code": "GB",
        "phone_number_type": "local",
        "porting_order_id": "072df5c8-567a-4bf0-a46f-46bbbac65fe5",
        "created_at": "2025-10-09T20:31:48.518554Z",
        "phone_number_range": {
            "start_at": "+441709241253",
            "end_at": "+441709241259"
        }
    }
}

You can associate multiple number ranges to your order. Just send a POST v2/porting_orders/:porting_order_id/associated_phone_numbers API request for each number range.

These ranges are not porting to Telnyx. Making this request does not add the phone numbers to the porting order to port over to Telnyx. This endpoint is solely used to communicate which other phone numbers on your losing carrier’s account should remain active and which should be disconnected on partial ports.

There are also endpoints to list which phone numbers you have associated to the order and an endpoint to delete any associated phone numbers from an order.