Genesys Cloud - Main

 View Only

Discussion Thread View

  • 1.  About Create "/api/v2/architect/ivrs" and Put "/api/v2/architect/ivrs/{ivrId}" API

    Posted 06-22-2022 05:00
    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
    #Integrations
    #Routing(ACD/IVR)

    ------------------------------
    嘉銘 杜
    Mitsui Knowledge Industry Co., Ltd
    ------------------------------


  • 2.  RE: About Create "/api/v2/architect/ivrs" and Put "/api/v2/architect/ivrs/{ivrId}" API

    Posted 06-22-2022 06:27
    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


  • 3.  RE: About Create "/api/v2/architect/ivrs" and Put "/api/v2/architect/ivrs/{ivrId}" API

    Posted 06-23-2022 05:46
    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


  • 4.  RE: About Create "/api/v2/architect/ivrs" and Put "/api/v2/architect/ivrs/{ivrId}" API

    Posted 06-27-2022 05:36
    Hi there,

    I am not sure if there is public documentation for this.

    You can add up to 100 numbers at a time. If you need to add more than that, your request has to follow this format:
    [Current DDI list] + [New DDIs]

    I.e. For 458 numbers:
    1st:      0 + [100]
    2nd: 100 + [100] 
    3rd:  200 + [100] 
    4th:  300 + [100] 
    5th:  400 + [58]
    Original Message


  • 5.  RE: About Create "/api/v2/architect/ivrs" and Put "/api/v2/architect/ivrs/{ivrId}" API

    Posted 06-30-2022 00:42
    Hi Paulo,

    Thank you for your explanation.

    Now I have knew how to use this Api to make a callroute with more than 100 DIDs.

    Thanks


    ------------------------------
    嘉銘 杜
    Mitsui Knowledge Industry Co., Ltd
    ------------------------------

    Original Message


  • 6.  RE: About Create "/api/v2/architect/ivrs" and Put "/api/v2/architect/ivrs/{ivrId}" API
    Best Answer

    GENESYS
    Posted 06-28-2022 12:55
    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.


  • 7.  RE: About Create "/api/v2/architect/ivrs" and Put "/api/v2/architect/ivrs/{ivrId}" API

    Posted 06-30-2022 00:45
    Hi Brad,

    Thank you for your explanation.

    Now I knew how it is work inside when use this api to make a callroute.
    Thanks for your support again.

    Thanks

    ------------------------------
    嘉銘 杜
    Mitsui Knowledge Industry Co., Ltd
    ------------------------------

    Original Message


  • 8.  RE: About Create "/api/v2/architect/ivrs" and Put "/api/v2/architect/ivrs/{ivrId}" API

    Posted 07-05-2023 10:52

    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


Need Help finding something?

Check out the Genesys Knowledge Network - your all-in-one access point for Genesys resources