Fetches all Recorders in Cambase.io
A documented Cambase.io operation that only reads, so it can watch for changes without altering anything. Describe what you want to happen and HumDay builds it.
What this operation does
Fetches all Recorders
- GETReads data · recorders
api.cambase.io/api/v1/recorders.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. Read-only access is still yours to grant, and still limited to what the contract needs.
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 RecorderPATCH · changes data
Questions
- Can HumDay fetches all recorders 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.
- Does this change anything in my Cambase.io account?
- No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in Cambase.io.
- 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.