Updates an existing Recorder in Cambase.io
A documented Cambase.io operation that changes something in your account. Describe the outcome you want in plain words — HumDay writes the program, proves it, and runs it.
What this operation does
Updates an existing Recorder
- PATCHChanges data · recorders
api.cambase.io/api/v1/recorders/{id}.json
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which Cambase.io operations the program may use, and this is one of them.
- You approve access. Because this one changes data, it cannot run until you have explicitly granted it.
Other Cambase.io operations
- Creates a new ModelPOST · changes data
- Creates a new VendorPOST · changes data
- Creates a new RecorderPOST · changes data
- Updates an existing ModelPATCH · changes data
- Updates an existing ModelPUT · changes data
- Updates an existing VendorPATCH · changes data
- Updates an existing VendorPUT · changes data
- Updates an existing RecorderPUT · changes data
Questions
- Can HumDay updates an existing recorder in Cambase.io?
- Yes. This operation is published in Cambase.io'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 Cambase.io data?
- Yes — this is a PATCH operation, so it changes something in Cambase.io. 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 Cambase.io account.
Where this came from
Read from a published API description for Cambase.io at api.cambase.io/api-docs/api-docs.json. The description above is the provider’s own wording, not ours. Last published 2018-12-31.