# 500 Internal error: GET /number\_management/numbers/{phoneNumberId}

**URL:** <https://devforum.zoom.us/t/500-internal-error-get-number-management-numbers-phonenumberid/139438>\
**Category:** Phone\
**Created:** [December 10, 2025, 7:47am UTC](https://devforum.zoom.us/t/500-internal-error-get-number-management-numbers-phonenumberid/139438 "2025-12-10T07:47:43Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![maxime.peccoux](https://avatars.discourse-cdn.com/v4/letter/m/13edae/32.png) [@maxime.peccoux](https://devforum.zoom.us/u/maxime.peccoux)\
**Post date:** [December 10, 2025, 7:47am UTC](https://devforum.zoom.us/t/500-internal-error-get-number-management-numbers-phonenumberid/139438/1 "2025-12-10T07:47:43Z")

</div>

Hello,

**Description**  
Since several days, the API to Get a phone number /number\_management/numbers/{phoneNumberId} returned a 500 Internal server Error.

Example:

```auto
GET https://api.zoom.us/v2/number_management/numbers
{
    "page_size": 30,
    "next_page_token": "pGmQFiI4LN42Gj90v6A07VDxhS1njWATOt2",
    "numbers": [
        {
            "id": "--hA53NERD6hbCjOEn2a-A",
            "number": "xxxxxxxxxxx",
            "allocated_product": "ZOOM_PHONE",

             ............

Tracking ID: WEB_fc449ad7f9fddf85ac30b86a0cacf4e8

```

We can see the ID **–hA53NERD6hbCjOEn2a-A** of this phone number.

Now if we get directly from the ID:

```auto
GET https://api.zoom.us/v2/number_management/numbers/--hA53NERD6hbCjOEn2a-A

{“errorCode”: -1,“message”: “Internal error”}

Tracking ID: WEB_ec7641da3299f385adfef3886d6ae15b

```

**Error?**  
{  
“errorCode”: -1,  
“message”: “Internal error”  
}

**How To Reproduce**  
_Steps to reproduce the behavior:_  
_1._ GET [https://api.zoom.us/v2/number\_management/numbers/{phoneNumberId}](https://api.zoom.us/v2/number_management/numbers/%7BphoneNumberId%7D)

---

<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:** [December 11, 2025, 3:41pm UTC](https://devforum.zoom.us/t/500-internal-error-get-number-management-numbers-phonenumberid/139438/2 "2025-12-11T15:41:49Z")

</div>

Hi @maxime.peccoux  
Thanks for reaching out to us!  
I’m not able to reproduce this on my end. I’m wondering whether the format of the number ID might be affecting the request.  
With the logs you share I escalated this internally and will get back to you with an update soon (internal ticket number for reference ZSEE-188919)

---

<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:** [December 12, 2025, 7:03pm UTC](https://devforum.zoom.us/t/500-internal-error-get-number-management-numbers-phonenumberid/139438/3 "2025-12-12T19:03:47Z")

</div>

Hey @maxime.peccoux  
Can you please confirm if this tracking ID is no older than 7 days? We are not able to track this request

---

<div class="post-metadata">

**Author:** ![maxime.peccoux](https://avatars.discourse-cdn.com/v4/letter/m/13edae/32.png) [@maxime.peccoux](https://devforum.zoom.us/u/maxime.peccoux)\
**Post date:** [December 15, 2025, 10:29am UTC](https://devforum.zoom.us/t/500-internal-error-get-number-management-numbers-phonenumberid/139438/4 "2025-12-15T10:29:09Z")

</div>

Hi @elisa.zoom,

Yes Tracking ID have been done the day I opened th topic.

I’ve checked today and I don’t have anymore the issue. Is there something change on your side ?

Thank you for your help

Best regards

Maxime

---

<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:** [December 15, 2025, 2:46pm UTC](https://devforum.zoom.us/t/500-internal-error-get-number-management-numbers-phonenumberid/139438/5 "2025-12-15T14:46:20Z")

</div>

Hi @maxime.peccoux  
Thanks for getting back to us. Happy to hear you don’t have this issue anymore. I am not aware of any changes on our end. I will keep an eye on this thread, in case this happen again feel free to reach out to me and I will be happy to escalate this
