Delete a Timesheet Entry in Avaza Documentation
A documented Avaza Documentation 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
Delete a Timesheet Entry
- DELETEChanges data · Expense
api.avaza.com/api/Expense
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 Avaza Documentation 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 Avaza Documentation operations
- Create new Payment and optionally assign payment allocationsPOST · changes data
- Create a new draft invoicePOST · changes data
- Create new Bill PaymentPOST · changes data
- Create new Schedule BookingPOST · changes data
- Create a new draft BillPOST · changes data
- Create a TaskPOST · changes data
- Create a ContactPOST · changes data
- Delete webhook subscription by URLDELETE · changes data
Questions
- Can HumDay delete a timesheet entry in Avaza Documentation?
- Yes. This operation is published in Avaza Documentation'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 Avaza Documentation data?
- Yes — this is a DELETE operation, so it changes something in Avaza Documentation. 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 Avaza Documentation account.
Where this came from
Read from a published API description for Avaza Documentation at api.avaza.com/swagger/docs/v1. The description above is the provider’s own wording, not ours. Last published 2023-03-06.