Create clocking record for authenticated user in Apacta
A documented Apacta 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
Create clocking record for authenticated user
- POSTChanges data · ClockingRecords
app.apacta.com/clocking_records
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 Apacta 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 Apacta operations
- Add a new contactPOST · changes data
- Add new formPOST · changes data
- Add user to companyPOST · changes data
- Create eventPOST · changes data
- Add a new field to a FormPOST · changes data
- Create a new invoice filePOST · changes data
- Upload a new image to a userPOST · changes data
- Add a new invoice line text templatePOST · changes data
Questions
- Can HumDay create clocking record for authenticated user in Apacta?
- Yes. This operation is published in Apacta'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 Apacta data?
- Yes — this is a POST operation, so it changes something in Apacta. 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 Apacta account.
Where this came from
Read from a published API description for Apacta at apidoc.apacta.com/swagger.yaml. The description above is the provider’s own wording, not ours. Last published 2023-03-06.