Can HumDay connect to Codat Sync for Commerce?

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

Do I need to write code to automate Codat Sync for Commerce?

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 Sync for Commerce account.

What can HumDay do in Codat Sync for Commerce?

8 of the 17 documented operations change something in Codat Sync for Commerce, and 9 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my Codat Sync for Commerce 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 Sync for Commerce is held behind that approval.

Automate Codat Sync for Commerce

HumDay reads Codat Sync for Commerce’s own published API description and derives 17 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.

What Codat Sync for Commerce is

The API for Sync for Commerce. Sync for Commerce is an API and a set of supporting tools. It has been built to enable e-commerce, point of sale platforms to provide high-quality integrations with numerous accounting platform through standardized API, seamlessly transforming business sale's data into accounting artefacts. [Read More...](https://docs.codat.io/sfc/overview)

API host: api.codat.io

What HumDay can do in Codat Sync for Commerce

8 documented operations change something in Codat Sync for Commerce.

POSTCreate a sync for commerce company/meta/companies/sync
POSTCreate a data connection/meta/companies/{companyId}/connections
POSTCreate or update configuration./config/companies/{companyId}/sync/commerce
PATCHUpdate preferences for text fields on sync flow/sync/commerce/config/ui/text
POSTRun a Commerce sync from the last successful sync/companies/{companyId}/sync/commerce/latest
PATCHUpdate data connection/meta/companies/{companyId}/connections/{connectionId}
POSTRun a Commerce sync from a given date range/meta/companies/{companyId}/sync/commerce/historic
PATCHUpdate the visible accounts on Sync Flow/sync/commerce/config/ui/accounts/platform/{commerceKey}

What HumDay can read from Codat Sync for Commerce

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

GETList companies/meta/companies
GETList information on Codat's supported integrations/config/integrations
GETList data connections/meta/companies/{companyId}/connections
GETRetrieve preferences for text fields on Sync Flow/sync/commerce/config/ui/text
GETGet branding for an integration/config/integrations/{platformKey}/branding
GETRetrieve config preferences set for a company./config/companies/{companyId}/sync/commerce
GETList visible accounts/clients/{clientId}/config/ui/accounts/platform/{platformKey}
GETGet status for a company's syncs/meta/companies/{companyId}/sync/commerce/status
GETRetrieve sync flow url/config/sync/commerce/{commerceKey}/{accountingKey}/start

How automating Codat Sync for Commerce works

Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
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.
See it proven. The program runs and shows you the result before it is allowed near your live Codat Sync for Commerce account.
Grant access, then go live. You approve the specific Codat Sync for Commerce operations it may use — and only those.