Create Payment in Apideck Accounting

What this operation does

Create Payment

• POSTChanges data · Paymentsunify.apideck.com/accounting/payments

How HumDay uses it

1. You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
2. The contract names it. Before anything is built, you see exactly which Apideck Accounting operations the program may use, and this is one of them.
3. You approve access. Because this one changes data, it cannot run until you have explicitly granted it.

Other Apideck Accounting operations

• Create Invoice ItemPOST · changes data
• Create InvoicePOST · changes data
• Create CustomerPOST · changes data
• Delete Invoice ItemDELETE · changes data
• Update Invoice ItemPATCH · changes data
• Delete InvoiceDELETE · changes data
• Update InvoicePATCH · changes data
• Delete PaymentDELETE · changes data

All 53 Apideck Accounting operations

Questions

Can HumDay create payment in Apideck Accounting?

Yes. This operation is published in Apideck Accounting'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 Apideck Accounting data?

Yes — this is a POST operation, so it changes something in Apideck Accounting. 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 Apideck Accounting account.

Where this came from

Read from a published API description for Apideck Accounting at raw.githubusercontent.com/apideck-libraries/openapi-specs/master/accounting.yml. The description above is the provider’s own wording, not ours. Last published 2023-04-19.