Update history item in ID4i

What this operation does

Update history item

• PATCHChanges data · History/api/v1/history/{id4n}/{organizationId}/{sequenceId}

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 ID4i 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 ID4i operations

• Add history itemPOST · changes data
• Register userPOST · changes data
• Create GUID(s)POST · changes data
• Create API keyPOST · changes data
• Create collectionPOST · changes data
• Create organizationPOST · changes data
• ID4i API LoginPOST · changes data
• Create an document for an id4nPOST · changes data

All 106 ID4i operations

Questions

Can HumDay update history item in ID4i?

Yes. This operation is published in ID4i'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 ID4i data?

Yes — this is a PATCH operation, so it changes something in ID4i. 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 ID4i account.

Where this came from

Read from a published API description for ID4i at backend.id4i.de/docs/swagger.json. The description above is the provider’s own wording, not ours. Last published 2023-03-06.