List payments in Codat Commerce

What this operation does

List payments

• GETReads data · Paymentsapi.codat.io/companies/{companyId}/connections/{connectionId}/data/commerce-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 Codat Commerce operations the program may use, and this is one of them.
3. You approve access. Read-only access is still yours to grant, and still limited to what the contract needs.

Other Codat Commerce operations

• List payment methodsGET · reads data
• List customersGET · reads data
• List disputesGET · reads data
• List productsGET · reads data
• List locationsGET · reads data
• List transactionsGET · reads data
• List tax componentsGET · reads data
• List product categoriesGET · reads data

All 11 Codat Commerce operations

Questions

Can HumDay list payments in Codat Commerce?

Yes. This operation is published in Codat Commerce'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 Codat Commerce account?

No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in Codat Commerce.

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 Codat Commerce account.

Where this came from

Read from a published API description for Codat Commerce at raw.githubusercontent.com/codatio/oas/main/json/Codat-Commerce.json. The description above is the provider’s own wording, not ours. Last published 2023-04-18.