Why no PATCH for ivr?

Platform API
1

In title really.
Why is there no PATCH verb for the ivr API ( /api/v2/architect/ivrs/{ivrId} )

Must be a common need/ask to dynamically add or remove many DiD numbers.

I have 1400 to create (easy enough) and to then assign to a flow. A Patch on DNS object would help considerably.

I searched and found old post on this Here but that does not offer up much more than stating a Patch does not exist.

Will work around it, but feels like a gap in API arsenal to me

Simon

2

Hi Simon,

A couple of things.

  1. Many of our APIs do not have PATCH methods. It is usually up to the individual service teams to decide if they want a path endpoint.

  2. You can still update the IVR record through the PUT endpoint. It is a little painful because you have to first read IVR record, update the values and then submit via the PATCH but it can be done.

  3. I am going to forward your post to the development team who owns the endpoints. I would also recommend you open an Ideas ticket here as our product management team uses the Idea portal to help harvest and prioritize product feature requests.

Thanks,
John Carnell
Director, Developer Engagement

3

Hi John,

I mentioned in OP I would work around it, and have already with GC CLI and powershell scripts to get ivr, store response and update the powershell object, back to json to the cli Update command.
Point is that is lot more effort than necessary if a PATCH verb existed, and prone to breaking the object (ivr routing in this case).

Some of the endpoints are really great candidates for PATCH, the ivr endpoint to manage the DNIS numbers is an obvious case.
As Genesys is ground up API and customer centric, I would imagine the service teams would consider the API and its usage when defining. Saying that Genesys is good at listening and adding items to the roadmap.

I do also create Aha suggestions but some get quickly lost in the volume of requests that happen, Probably with such a number of requests some of the API ones may seem quite niche.

I also develop restful web services, and adding a PATCH is almost mandatory.

Simon

4

Hi Simon,

Totally understand and don't disagree. As I said, I will also post to the dev team and see if they might already have something in the works.

Thanks,
John Carnell

1 Like
5

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