Automate Codat Expense

What Codat Expense is

The API for Sync for Expenses. Sync for Expenses is an API and a set of supporting tools. It has been built to enable corporate card and expense management platforms to provide high-quality integrations with multiple accounting platforms through a standardized API. [Read more...](https://docs.codat.io/sync-for-expenses/overview) [See our OpenAPI spec](https://github.com/codatio/oas)

API host: api.codat.io

What HumDay can do in Codat Expense

5 documented operations change something in Codat Expense.

• POSTCreate expense-transactions/companies/{companyId}/sync/expenses/data/expense-transactions
• POSTCreate Partner Expense connection/companies/{companyId}/sync/expenses/connections/partnerExpense
• POSTInitiate sync/companies/{companyId}/sync/expenses/syncs
• POSTSet company configuration/companies/{companyId}/sync/expenses/config
• POSTUpload attachment/companies/{companyId}/sync/expenses/syncs/{syncId}/transactions/{transactionId}/attachments

What HumDay can read from Codat Expense

These are the operations a schedule or a trigger can watch.

• GETList sync statuses/companies/{companyId}/sync/expenses/syncs/list/status
• GETGet company configuration/companies/{companyId}/sync/expenses/config
• GETMapping options/companies/{companyId}/sync/expenses/mappingOptions
• GETLatest sync status/companies/{companyId}/sync/expenses/syncs/latest/status
• GETLast successful sync/companies/{companyId}/sync/expenses/syncs/lastSuccessful/status
• GETGet Sync status/companies/{companyId}/sync/expenses/syncs/{syncId}/status
• GETGet Sync transactions/companies/{companyId}/sync/expenses/syncs/{syncId}/transactions
• GETGet Sync Transaction/companies/{companyId}/sync/expenses/syncs/{syncId}/transactions/{transactionId}

How automating Codat Expense works

1. Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
2. Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
3. See it proven. The program runs and shows you the result before it is allowed near your live Codat Expense account.
4. Grant access, then go live. You approve the specific Codat Expense operations it may use — and only those.

Automate Codat Expense with these

• Codat Accounting105 operations
• Codat Assess18 operations
• Codat Bank Feeds6 operations
• Codat Banking5 operations
• Codat Commerce11 operations
• Codat Sync for Commerce17 operations
• Stripe442 operations
• Zuora Reference Billing428 operations
• bunq421 operations
• PayRun.IO389 operations
• Sinao272 operations
• Xero Accounting224 operations

Categories

• Finance

Questions about Codat Expense automation

Can HumDay connect to Codat Expense?

Yes. HumDay reads Codat Expense's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 13 operations are documented.

Do I need to write code to automate Codat Expense?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Codat Expense account.

What can HumDay do in Codat Expense?

5 of the 13 documented operations change something in Codat Expense, and 8 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my Codat Expense account safe?

Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to Codat Expense is held behind that approval.

Where this came from

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