Get a list of payment terms in Apacta
A documented Apacta 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
Get a list of payment terms
- GETReads data · PaymentTerms
app.apacta.com/payment_terms
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. Read-only access is still yours to grant, and still limited to what the contract needs.
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 clocking record for authenticated userPOST · changes data
- Create a new invoice filePOST · changes data
- Upload a new image to a userPOST · changes data
Questions
- Can HumDay get a list of payment terms 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.
- Does this change anything in my Apacta account?
- No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in Apacta.
- 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.