List sync statuses in Codat Expense
A documented Codat Expense 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
List sync statuses
- GETReads data · Sync status
api.codat.io/companies/{companyId}/sync/expenses/syncs/list/status
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 Codat Expense 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 Codat Expense operations
- Create expense-transactionsPOST · changes data
- Create Partner Expense connectionPOST · changes data
- Initiate syncPOST · changes data
- Set company configurationPOST · changes data
- Upload attachmentPOST · changes data
- Get company configurationGET · reads data
- Mapping optionsGET · reads data
- Latest sync statusGET · reads data
Questions
- Can HumDay list sync statuses 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.
- Does this change anything in my Codat Expense 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 Expense.
- 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.