# Zoom Phone API - Determining line\_key\_id

**URL:** <https://devforum.zoom.us/t/zoom-phone-api-determining-line-key-id/128312>\
**Category:** API and Webhooks\
**Created:** [February 24, 2025, 4:06pm UTC](https://devforum.zoom.us/t/zoom-phone-api-determining-line-key-id/128312 "2025-02-24T16:06:39Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![gpieroni](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/gpieroni/32/65096_2.png) [@gpieroni](https://devforum.zoom.us/u/gpieroni)\
**Post date:** [February 24, 2025, 4:06pm UTC](https://devforum.zoom.us/t/zoom-phone-api-determining-line-key-id/128312/1 "2025-02-24T16:06:39Z")

</div>

**API Endpoint(s) and/or Zoom API Event(s)**

> **[Phone APIs - Zoom Developers](https://developers.zoom.us/docs/api/phone/#tag/line-keys/PATCH/phone/extension/%7BextensionId%7D/line_keys)**
>
> API reference for: Phone

**Description**  
Is there a way to determine the **line\_key\_id** parameter on an unused line key?

If the key has previously been defined I can perform a **GET** first and record the **line\_key\_id** values and then use that to update the line key, but if the key is blank nothing is returned.

It seems I may have to upload dummy keys (speed dials or something similar) via CSV on Zoom Phone web first so I can then perform a **GET** to capture the **line\_key\_id** , and then finally perform a **PATCH** to update the keys to what I actually need.

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [February 25, 2025, 9:19pm UTC](https://devforum.zoom.us/t/zoom-phone-api-determining-line-key-id/128312/2 "2025-02-25T21:19:30Z")

</div>

Hey @gpieroni  
Thanks for reaching out to us and welcome to the Zoom Developer Forum!  
Allow me some time to troubleshoot this on my end and I will get back to you with some updates

---

<div class="post-metadata">

**Author:** ![gpieroni](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/gpieroni/32/65096_2.png) [@gpieroni](https://devforum.zoom.us/u/gpieroni)\
**Post date:** [February 26, 2025, 1:09pm UTC](https://devforum.zoom.us/t/zoom-phone-api-determining-line-key-id/128312/3 "2025-02-26T13:09:25Z")

</div>

Hi Elisa - thank you, appreciate it!

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [March 4, 2025, 12:24am UTC](https://devforum.zoom.us/t/zoom-phone-api-determining-line-key-id/128312/4 "2025-03-04T00:24:16Z")

</div>

Hey @gpieroni  
Sorry for the late reply here! I am not able to troubleshoot this on my end.  
Would you be able to share with me the response body that you get when you can GET the line\_key\_id values and also the instance where you do not get anything back in your response.  
I will be helpful if you could share the tracking ID of the requests found in the response headers.

---

<div class="post-metadata">

**Author:** ![gpieroni](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/gpieroni/32/65096_2.png) [@gpieroni](https://devforum.zoom.us/u/gpieroni)\
**Post date:** [March 4, 2025, 12:54pm UTC](https://devforum.zoom.us/t/zoom-phone-api-determining-line-key-id/128312/5 "2025-03-04T12:54:34Z")

</div>

Hi Elisa -

The issue is I’m trying to determine **line\_key\_id** for unused line keys. Here’s an example of a common area phone with line keys defined for keys 1, 2 and 3.

 ![keys](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/a/3/a3287db71ce894c04299fb44ce84bf2fa2977593.png)

Here’s the body that’s returned. How do I determine **line\_key\_id** for the blank line keys 4, 5, 6, etc ?

> {  
> “line\_keys”: [  
> {  
> “line\_key\_id”: “C-pkLKSyQaqV-82iBcNDyA”,  
> “index”: 1,  
> “type”: “line”,  
> “key\_assignment”: {  
> “extension\_id”: “iki1nxoXRqGSbbskOwtzMw”,  
> “extension\_number”: “801301”,  
> “phone\_number”: “”,  
> “display\_name”: “Boston VO 01”  
> },  
> “alias”: “801301”,  
> “outbound\_caller\_id”: “anonymous”  
> },  
> {  
> “line\_key\_id”: “NQnLrTK9T9Gl2kgUvFdqsQ”,  
> “index”: 2,  
> “alias”: “801301”,  
> “outbound\_caller\_id”: “anonymous”  
> },  
> {  
> “line\_key\_id”: “uWpi8snZTL28cqkrJP1bQA”,  
> “index”: 3,  
> “alias”: “801301”,  
> “outbound\_caller\_id”: “anonymous”  
> }  
> ]  
> }

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [March 5, 2025, 2:21pm UTC](https://devforum.zoom.us/t/zoom-phone-api-determining-line-key-id/128312/6 "2025-03-05T14:21:56Z")

</div>

Hey @gpieroni  
It seems like the line\_key\_id will get generated once it is assigned, so as you mentioned in the first post, uploading dummy keys might do the trick as a workaround for now.  
I will send you a DM to get more details and will create a ticket for our Engineering team so they can determine if this is expected behavior or a bug on our end

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [March 14, 2025, 3:15pm UTC](https://devforum.zoom.us/t/zoom-phone-api-determining-line-key-id/128312/7 "2025-03-14T15:15:14Z")

</div>

To update this thread.  
This is expected behavior, the line\_key\_id gets generated once its assigned

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/6/1/614bdd549b610bbaa46ff934617683a02bdaa03c.png) [@system](https://devforum.zoom.us/u/system)\
**Post date:** [March 15, 2025, 3:15pm UTC](https://devforum.zoom.us/t/zoom-phone-api-determining-line-key-id/128312/8 "2025-03-15T15:15:28Z")

</div>

Closed on March 15, 2025, 3:15pm UTC

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.
