Zoom Phone Line Keys API does not support all possible line types

Phone
1

I’m trying to use Batch update line keys to update keys and positions for Zoom phone users. I’m finding that the API does not fully support all the possible line types and this is severely limiting its usefulness.

As an example, I’ve configured a user with a position for all the line types available. Here’s the csv export:

Key,Key Type,Key Assignment,Alias,Outbound Caller ID
1," Line"," Ext.555123,(216) 770-6792"," Primary Lne 1"," Same as Number"
2," Line"," Ext.1001(Shared)"," Shared Line 2"," Same as Number"
3," Line(Duplicated)"," Ext.555123,(216) 770-6792"," Duplicate Line 3"," (872) 870-8270"
4," Speed Dial"," 12345"," Speed Dial 4",
5," Call Park"," *801"," Call Park 5",
6," BLF"," Ext.77101"," BLF 6",
7," Zoom Meeting",," Zoom Meeting 7",
8," Paging-Standard"," Ext.999042"," Paging Standard 8",
9," Paging-Emergency"," Ext.999042"," Paging Emergency 9",

Below is the Get line keys response for the same user.

{
    "line_keys":
    [
        {
            "alias": "Primary Lne 1",
            "index": 1,
            "key_assignment":
            {
                "display_name": "XXX",
                "extension_id": "T2BJWex0Q0Kt6afJeEaVHw",
                "extension_number": "555123",
                "phone_number": "+1XXX7706792"
            },
            "line_key_id": "bS153vM4ThGXXPnbeBOG_g",
            "outbound_caller_id": "+XXX7706792",
            "type": "line"
        },
        {
            "alias": "Shared Line 2",
            "index": 2,
            "key_assignment":
            {
                "display_name": "XXX",
                "extension_id": "WV0AMAe8RhGFop5wV75RWA",
                "extension_number": "1001",
                "phone_number": ""
            },
            "line_key_id": "fULDgLoJTi2t43F1f8BRbA",
            "type": "line"
        },
        {
            "alias": "Duplicate Line 3",
            "index": 3,
            "line_key_id": "02OwytxLQe2QZmcUajKIOQ",
            "outbound_caller_id": "+1XXX8708270"
        },
        {
            "alias": "Speed Dial 4",
            "index": 4,
            "key_assignment":
            {
                "speed_dial_number": "12345"
            },
            "line_key_id": "ffPWQOc9RbauWghY6PLp0w",
            "type": "speed_dial"
        },
        {
            "alias": "Call Park 5",
            "index": 5,
            "key_assignment":
            {
                "retrieval_code": "*801"
            },
            "line_key_id": "AjZyDY23RsOk6mJsTwaURA",
            "type": "call_park"
        },
        {
            "alias": "BLF 6",
            "index": 6,
            "key_assignment":
            {
                "display_name": "XXX",
                "extension_id": "TZWiTwqTT-eiihJsF_O0mQ",
                "extension_number": "77101"
            },
            "line_key_id": "JBlgwIuhSgK546YnN9Df1w",
            "type": "blf"
        },
        {
            "alias": "Zoom Meeting 7",
            "index": 7,
            "line_key_id": "XYvZ3mJST2--jxSkJx1HAQ",
            "type": "zoom_meeting"
        },
        {
            "alias": "Paging Standard 8",
            "index": 8,
            "key_assignment": {},
            "line_key_id": "yJcWLiPbSmuQn12QrRkerw"
        },
        {
            "alias": "Paging Emergency 9",
            "index": 9,
            "key_assignment": {},
            "line_key_id": "JDFJ2WqgRjmL6Ez_syaWPQ"
        }
    ]
}

Notice the following issues:

  • The duplicate line at index: 3 entry does not include a type property.
  • The paging standard line at index: 8 does not include a type property and the key_assignment is empty.
  • The paging emergency line at index: 9 does not include a type property and the key_assignment is empty.

The missing elements mean that I cannot add lines of these types through the API and cannot identify them for the purposes of reporting.

Can you please let me know if API support for all possible line types is planned?

Please also let me know if you need additional information.

Thank you.

2

Hi @kris.seraphine
Thanks for reaching out to us!
I will take a look into this and will get back to you with an update

3

Hey @kris.seraphine
I just wanted to update you here
I created a ticket for our Engineering team ,and we are currently looking into this (ZSEE-159439 internal ticket number for reference)