Skip to content
E-commerce platforms

codat.io:sync-for-commerce

Sync for Commerce sandbox and mock API

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) Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
17
Collections
-
Event types
-
Start this simulation
example request
curl https://your-codat-sync-for-commerce.slurry.io/config/integrations \
  -H "Authorization: Bearer slurry_sim_..."

Your simulation gets its own hostname, key and IP allow-list. Built from API version 1.1.

What gets simulated

Collections, relationships and state machines are worked out from the spec when you start the simulation.

  • State. Creates, updates and deletes persist and show up in later reads.
  • Behaviour. Records move through their states on a schedule you control, and you can fast-forward up to 30 days.
  • Webhooks. Every change emits a signed, retried event.
  • Failure. Per-endpoint errors, latency and chaos rules, on demand.

Operations

First 12 of 17.

  • GET/clients/{clientId}/config/ui/accounts/platform/{platformKey}
  • POST/companies/{companyId}/sync/commerce/latest
  • GET/config/companies/{companyId}/sync/commerce
  • POST/config/companies/{companyId}/sync/commerce
  • GET/config/integrations
  • GET/config/integrations/{platformKey}/branding
  • GET/config/sync/commerce/{commerceKey}/{accountingKey}/start
  • GET/meta/companies
  • POST/meta/companies/sync
  • GET/meta/companies/{companyId}/connections
  • POST/meta/companies/{companyId}/connections
  • PATCH/meta/companies/{companyId}/connections/{connectionId}