API v2 Without PATCH — How Are You Handling Partial Updates?

1

Hi everyone,

I’ve been working with the Manager API and feel fairly comfortable with it overall, but I’ve run into a limitation when using API v2.

In API v1, the PATCH method is available, which makes it easy to update a single field without affecting the rest of the data. However, in API v2, it seems that PATCH is no longer supported. Using PUT instead causes the entire record to be overwritten, which isn’t ideal when I only need to modify one field.

At the moment, my workaround is to fall back to API v1 specifically for PATCH requests, while using API v2 for everything else. That said, I’d strongly prefer to rely entirely on API v2 going forward, especially for future compatibility and support.

Is there a recommended way to handle partial updates in API v2, or are there plans to support PATCH (or similar functionality) in the future?

image
image958×521 33.7 KB

image
image968×646 37.1 KB

2

Hello @mohamedbreky,

The solution is simple, you should GET first, then PUT.

However, I can definitely see the benifit of using PATCH which will reduce the number of calls required for updates.

But, then again, this has been discussed many times before and it was not once made it into ideas, so unfortunately, we will have to settle for GET and PUT for the foreseen future.