Partially update a json bin with JSON Merge Patch in Extendsclass JSON storage

What this operation does

Partially update a json bin with JSON Merge Patch

• PATCHChanges dataextendsclass.com/bin/{id}

How HumDay uses it

1. You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
2. The contract names it. Before anything is built, you see exactly which Extendsclass JSON storage operations the program may use, and this is one of them.
3. You approve access. Because this one changes data, it cannot run until you have explicitly granted it.

Other Extendsclass JSON storage operations

• Create a json binPOST · changes data
• Delete a json binDELETE · changes data
• Update a json binPUT · changes data
• Return a json binGET · reads data

All 5 Extendsclass JSON storage operations

Questions

Can HumDay partially update a json bin with json merge patch in Extendsclass JSON storage?

Yes. This operation is published in Extendsclass JSON storage's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.

Will this change my Extendsclass JSON storage data?

Yes — this is a PATCH operation, so it changes something in Extendsclass JSON storage. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.

Do I need to write code?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Extendsclass JSON storage account.

Where this came from

Read from a published API description for Extendsclass JSON storage at extendsclass.com/json-storage.openapi.json. The description above is the provider’s own wording, not ours. Last published 2021-01-18.