Automate Avaza Documentation
HumDay reads Avaza Documentation’s own published API description and derives 86 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.
What Avaza Documentation is
Welcome to the autogenerated documentation & test tool for Avaza's API. API Security & Authentication Authentication options include OAuth2 Implicit and Authorization Code flows, and Personal Access Token. All connections should be encrypted over SSL/TLS You can set up and manage your api authentication credentials from within your Avaza account. (requires
API host: api.avaza.com
What HumDay can do in Avaza Documentation
36 documented operations change something in Avaza Documentation.
- POSTCreate new Payment and optionally assign payment allocations to Invoices
/api/Payment - POSTCreate a new draft invoice
/api/Invoice - POSTCreate new Bill Payment and optionally assign payment allocations to Bills
/api/BillPayment - POSTCreate new Schedule Booking
/ScheduleSeries/AddBooking - POSTCreate a new draft Bill
/api/Bill - POSTCreate a Task
/api/Task - POSTCreate a Contact
/api/Contact - DELETEDelete webhook subscription by URL
/api/Webhook - POSTSubscribe to Webhook. On success, returns ID of webhook subscription.
/api/Webhook - POSTCreate a new draft Estimate
/api/Estimate - POSTCreate a new Timesheet Entry
/api/Timesheet - POSTCreate new Leave Booking
/ScheduleSeries/AddLeave - DELETEDelete Webhook Subscription by ID
/api/Webhook/{id} - DELETEDelete a Task
/api/Task - PUTUpdate a Task.
/api/Task - POSTCreate a Company
/api/Company - PUTUpdate a Company record.
/api/Company - POSTCreate an Expense
/api/Expense - POSTCreate a Project
/api/Project - POSTCreate a Section
/api/Section - POSTAssign a user as a Member of a Project
/api/ProjectMember - DELETEDelete a Timesheet Entry
/api/Expense - PUTUpdate an Expense
/api/Expense - PUTUpdate an Project
/api/Project - DELETEDelete a Section
/api/Section - PUTUpdate a Timesheet
/api/Timesheet - PUTUpdate a Member of a Project
/api/ProjectMember - POSTSubmit Timesheets for Approval.
/api/TimesheetSubmission - PUTEdit Leave Booking
/ScheduleSeries/EditLeave - PUTEdit Booking
/ScheduleSeries/EditBooking - POSTAssign a TimeSheetCategory to a Project.
/api/ProjectTimesheetCategory - POSTSubmit Expenses for Approval.
/api/ExpenseApproval/Submit - DELETEDelete a Timesheet Entry
/api/Timesheet/{id} - DELETEStop the timer running on an existing Timesheet Entry
/api/TimesheetTimer/{id} - POSTStarts a Timer running on an existing Timesheet Entry
/api/TimesheetTimer/{id} - POSTUpdate Attachment
/api/Expense/Attachment
What HumDay can read from Avaza Documentation
These are the operations a schedule or a trigger can watch.
- GETGets minimal list of Tasks for the current user
/api/Task/Lookup - GETGets list of Tasks
/api/Task - GETGets list of Contacts
/api/Contact - GETGets list of Invoices
/api/Invoice - GETGets list of Payments
/api/Payment - GETGet list of Webhook Subscriptions
/api/Webhook - GETGets list of Task Types
/api/TaskType - GETGets list of Task Statuses
/api/TaskStatus - GETGets list of Bill Payments
/api/BillPayment - GETGets list of Schedule Series
/api/ScheduleSeries - GETGets list of Schedule Assignments.
/api/ScheduleAssignment - GETGets minimal list of active Projects for the current user
/api/Project/Lookup - GETGets minimal list of Expense Payment Methods.
/api/ExpensePaymentMethod/Lookup - GETGet Webhook Subscription by SubscriptionID
/api/Webhook/{id} - GETGet List of Taxes configured in the Avaza account.
/api/Tax - GETGets list of Bills
/api/Bill - GETGets list of Companies
/api/Company - GETGets list of Expenses
/api/Expense - GETGets list of Projects
/api/Project - GETGets list of Sections
/api/Section - GETGets list of Currencies
/api/Currency - GETGets list of Estimates
/api/Estimate - GETGets list of Inventory
/api/Inventory - GETGets list of Timsheets
/api/Timesheet - GETGets list of CreditNotes
/api/CreditNote - GETGets list of Fixed Amounts
/api/FixedAmount - GETGet Collection of Users who have roles in the current Avaza account.
/api/UserProfile - GETGets list of Project Members
/api/ProjectMember - GETGets the Running Timer if there is one for a user.
/api/TimesheetTimer - GETGets list of Expense Categories
/api/ExpenseCategory - GETGets list of Project Timesheet Categories
/api/ProjectTimesheetCategory - GETGets minimal list of Companies.
/api/Company/Lookup - GETGets minimal list of Expense Groups.
/api/ExpenseGroup/Lookup - GETGets minimal list of Expense Merchants.
/api/ExpenseMerchant/Lookup - GETGets Task by Task ID
/api/Task/{id} - GETGets Contact by Contact ID
/api/Contact/{id} - GETGets Invoice by Invoice ID
/api/Invoice/{id} - GETGets Payment by Payment Transaction ID
/api/Payment/{id} - GETGets a Bill Payment by Payment Transaction ID
/api/BillPayment/{id} - GETAccount Details
/api/Account - GETGets Basic Summary of Expense Statistics
/api/ExpenseSummary - GETGets Basic Summary of Timesheet Statistics
/api/TimesheetSummary - GETGets a Bill by Bill ID
/api/Bill/{id} - GETGets Company by Company ID
/api/Company/{id} - GETGets an Expense Entry by Expense ID
/api/Expense/{id} - GETGets Project by Project ID
/api/Project/{id} - GETGets Estimate by Estimate ID
/api/Estimate/{id} - GETGets InventoryItem by InventoryItem ID
/api/Inventory/{id} - GETGets a Timesheet Entry by Timesheet ID
/api/Timesheet/{id} - GETGets Credit Note by CreditNoteID
/api/CreditNote/{id}
How automating Avaza Documentation works
- Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
- Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
- See it proven. The program runs and shows you the result before it is allowed near your live Avaza Documentation account.
- Grant access, then go live. You approve the specific Avaza Documentation operations it may use — and only those.
Automate Avaza Documentation with these
- GitHub811 operations
- Trello324 operations
- Bitbucket292 operations
- Orthanc Server Orthanc268 operations
- Asana249 operations
- Discord242 operations
- Slack174 operations
- Visualstudio VSOnline152 operations
- OnSched Setup138 operations
- StackExchange124 operations
- Slicebox118 operations
- Noosh application102 operations
Categories
Questions about Avaza Documentation automation
- Can HumDay connect to Avaza Documentation?
- Yes. HumDay reads Avaza Documentation's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 86 operations are documented.
- Do I need to write code to automate Avaza Documentation?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Avaza Documentation account.
- What can HumDay do in Avaza Documentation?
- 36 of the 86 documented operations change something in Avaza Documentation, and 50 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my Avaza Documentation account safe?
- Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to Avaza Documentation is held behind that approval.
Where this came from
The operations above are read from a published API description for Avaza Documentation at api.avaza.com/swagger/docs/v1. Descriptions are the provider’s own words, not ours. Last published 2023-03-06.