Set company configuration in Codat Expense

What this operation does

Set company configuration

• POSTChanges data · Configurationapi.codat.io/companies/{companyId}/sync/expenses/config

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 Expense 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 Codat Expense operations

• Create expense-transactionsPOST · changes data
• Create Partner Expense connectionPOST · changes data
• Initiate syncPOST · changes data
• Upload attachmentPOST · changes data
• List sync statusesGET · reads data
• Get company configurationGET · reads data
• Mapping optionsGET · reads data
• Latest sync statusGET · reads data

All 13 Codat Expense operations

Questions

Can HumDay set company configuration in Codat Expense?

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

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

Where this came from

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