May be of use to some while no PATCH verb available.
Original Message:
Sent: 08-28-2024 08:51
From: Denis Ridel-Pfeffer
Subject: About Create "/api/v2/architect/ivrs" and Put "/api/v2/architect/ivrs/{ivrId}" API
You can vote for this idea:
https://genesyscloud.ideas.aha.io/ideas/OPGCV-I-65
It requests a new PATCH endpoint that will allow to add new DIDs to existing Call Routes.
Currently you can either POST (create a new Call Route with maximum of 100 DIDs) or PUT (replace existing DIDs in an existing Call Route with maximum of 100 new DIDs).
------------------------------
Denis Ridel-Pfeffer
Intrum AB
Original Message:
Sent: 07-05-2023 10:52
From: Simon Brown
Subject: About Create "/api/v2/architect/ivrs" and Put "/api/v2/architect/ivrs/{ivrId}" API
I have similar problem, dropped down to 50 new did per PUT, also added a 10 second delay between PUT calls, it still fails! (using gc.exe in powershell)
Support ticket raised.
Very strange API behaviour deployed here (Give us a PATCH verb) and NOT documented still on the API site.
------------------------------
Simon Brown
Maintel Europe Limited
Original Message:
Sent: 06-28-2022 12:54
From: Brad Murlin
Subject: About Create "/api/v2/architect/ivrs" and Put "/api/v2/architect/ivrs/{ivrId}" API
The rate limit comes into play downstream - for each number you add the system has to query and confirm the DID Pool above the number, which runs 100 times for 100 net-new numbers - sometimes you can go above 100 per batch, sometimes you only get 75 -- I had a case open for this and was told 'it's sort of just how it works' -- you can get up to several thousand numbers total for one IVR, you just have to slowly append that number list to be bigger and bigger in small chunks.
------------------------------
Brad Murlin
Zillow, Inc.
Original Message:
Sent: 06-23-2022 05:46
From: 嘉銘 杜
Subject: About Create "/api/v2/architect/ivrs" and Put "/api/v2/architect/ivrs/{ivrId}" API
Hi Paulo,
Thanks for your answer.
And please let me ask a few more questions.
"You can only add 100 numbers at a time. The limitation is the total of NEW numbers you have in the payload."
Is there a document with the above restrictions?
For example, I would like to know in advance if other APIs have similar restrictions in the future.
"After associating the first 100 DDIs, you can run the request a second time and include all the numbers (160) to upsert data."
Regarding the above, I think that the Update API will be used from the second time,
Is there a limit on the number from the second time?
For example, can I register 100 for the first time and 500 for the second time (including 100 for the first time)?
I apologize for the inconvenience, but I would appreciate it if you could answer.
Thank you
------------------------------
嘉銘 杜
Mitsui Knowledge Industry Co., Ltd
Original Message:
Sent: 06-22-2022 06:26
From: Paulo Mesquita
Subject: About Create "/api/v2/architect/ivrs" and Put "/api/v2/architect/ivrs/{ivrId}" API
You can only add 100 numbers at a time. The limitation is the total of NEW numbers you have in the payload.
After associating the first 100 DDIs, you can run the request a second time and include all the numbers (160) to upsert data.
Original Message:
Sent: 06-22-2022 04:59
From: 嘉銘 杜
Subject: About Create "/api/v2/architect/ivrs" and Put "/api/v2/architect/ivrs/{ivrId}" API
Hello,
We are running into problems using this IVR API.
"/ Api / v2 / architect / ivrs"
We are trying to register 160 addresses (DIDs) in one IVR (Call Routing).
However, when I ran the API, I got an error which the rate limit was reached.
So, after trying various things, when I changed the address (DID) to 100, the execution was successful with the API without any problem. When I want to register 100 or more addresses, I need execute it multiple times.(The second time feels like adding the address (DID) to the first time'address (DID), and the API used at that time is "/ api / v2 / architect / ivrs / {ivrId}")
The rate limit information we currently know is below, but in this case, does anyone know which rate limit is stuck?
Also, does the internal logic of the "/ api / v2 / architect / ivrs" API register DIDs one by one with different APIs which is cause to the limit?
Or is there a limit to the maximum number that can be entered in the ["dnis": [],]of the "/ api / v2 / architect / ivrs" API?
{
"name": "",
"division": {
"name": ""
},
"description": "",
"version": 0,
"dateCreated": "",
"dateModified": "",
"modifiedBy": "",
"createdBy": "",
"modifiedByApp": "",
"createdByApp": "",
"dnis": [],
"openHoursFlow": {
"id": "",
"name": "",
"selfUri": ""
},
"closedHoursFlow": {
"id": "",
"name": "",
"selfUri": ""
},
"holidayHoursFlow": {
"id": "",
"name": "",
"selfUri": ""
},
"scheduleGroup": {
"id": "",
"name": "",
"selfUri": ""
}
}
If anyone knows, I would appreciate it if you could let me know.
Thank you
#API/Integrations
#Routing (ACD/IVR)
------------------------------
嘉銘 杜
Mitsui Knowledge Industry Co., Ltd
------------------------------