Zoom Phone API - not created an Auto Receptionist IVR via 'add an auto receptionist' API

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

POST /phone/auto_receptionists

Description

When adding an auto receptionist via this API, the related IVR resources are not automatically created. On the other hand, when created via Zoom’s UI (Admin Console), IVR resources are confirmed to be created. According to Zoom’s API documentation of IVR, there is no API to add an auto receptionist IVR, so we expect either the auto receptionist addition API to automatically create IVR or the provision of an API to create IVR.

Error?
n/a

How To Reproduce
Steps to reproduce the behavior:

  1. Execute POST https://api.zoom.us/v2/phone/auto_receptionists with body (parameters)
  2. Execute GET https://api.zoom.us/v2/phone/auto_receptionists/xxxxxx/ivr
  3. Return empty response
# Case: add an auto receptionists via API
curl -i -H 'Content-Type: application/json' -H "Authorization: Bearer $token" https://api.zoom.us/v2/phone/auto_receptionists/xxxxxx/ivr
HTTP/2 200
date: Tue, 18 Mar 2025 10:35:09 GMT
content-length: 0
x-zm-trackingid: WEB_ab6e62d39f2fa996512efd3bca541383
x-zm-region: VA2
vary: Origin
vary: Access-Control-Request-Method
vary: Access-Control-Request-Headers
x-frame-options: deny
x-ratelimit-category: Light
strict-transport-security: max-age=31536000; includeSubDomains
x-content-type-options: nosniff
# Case: add an auto receptionists via UI (Admin Console)
curl -i -H 'Content-Type: application/json' -H "Authorization: Bearer $token" https://api.zoom.us/v2/phone/auto_receptionists/yyyyyyyyy/ivr
HTTP/2 200
date: Tue, 18 Mar 2025 10:37:09 GMT
content-type: application/json
content-length: 356
x-zm-trackingid: WEB_41caa82c47f6e3f197df4c24e4224e80
x-zm-region: VA2
vary: Origin
vary: Access-Control-Request-Method
vary: Access-Control-Request-Headers
x-frame-options: deny
x-ratelimit-category: Light
strict-transport-security: max-age=31536000; includeSubDomains
x-content-type-options: nosniff

{"audio_prompt":{"id":"","name":"Default"},"key_actions":[{"key":"0","action":100,"target":{"id":"ddddddddddddd","extension_id":"qqqqqqqqqqqqqqq","display_name":"test-tonishi","extension_number":"300"},"voicemail_greeting":{"id":"","name":"Default"}},{"key":"*","action":21}],"caller_enters_no_action":{"action":-1,"audio_prompt_repeat":3}}

Hi @tonishi
Thanks for reaching out to us!
I will look into this and will get back to you with an update

1 Like

Hi There!
@tonishi
I am not able to replicate this on my end.
When i query the GEt https://api.zoom.us/v2/phone/auto_receptionists/xxxxxx/ivr endpoint, I do get all the data back in my response.

@elisa.zoom
Thank you for looking into this.

In my environment, this issue only occurred with the auto receptionist resource. However, the fact remains that this issue is happening.

Are we supposed to develop our application with the assumption that the IVR GET API might return an empty body?

Hi @tonishi
I am not able to replicate/understand this.
Could you please share the request body you are sending when you create an autoreceptionist so I can try and run the same query on my end