Sync for Commerce

Name: Sync for Commerce API
Brand: Sync for Commerce
Availability: InStock

✓ Official Vendor SpecE CommerceOrder ManagementapiKey22 EndpointsREST

For Agents

Configure and trigger automated sync of a merchant's commerce sales, fees, and refunds into their accounting software, with integration branding and lifecycle controls.

Connect the Sync for Commerce to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Sync for Commerce, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Sync for Commerce API.

Configure a Sync for Commerce connection between a commerce source and an accounting destination

Trigger and monitor scheduled syncs of sales, fees, and refunds into the accounting platform

Manage company and connection records that tie merchants to their sync configuration

Authorize accounting connections via the connection authorization flow

GET STARTED

Start building with Sync for Commerce API

Explore with Jentic

View OpenAPI Document

Use for: I want to start a Sync for Commerce flow between Shopify and QuickBooks, List all sync integrations available for a merchant, Get the sync configuration for a specific merchant company, Authorize a merchant's accounting connection for sync

Not supported: Does not handle reading commerce data, payment processing, or general ledger CRUD — use for the configuration and execution of automated sync from a commerce platform into accounting software only.

Codat's Sync for Commerce API automates the daily push of commerce platform sales, fees, and refunds into a merchant's accounting software. It manages the connection lifecycle between a commerce source (Shopify, Square, Stripe) and an accounting destination (QuickBooks, Xero, Sage), exposes sync configuration and integration metadata, and provides advanced controls for partners embedding the experience. Commerce platforms and reseller partners use it to ship a 'sync to accounting' feature without per-platform engineering.

Use Cases

Patterns agents use Sync for Commerce API for, with concrete tasks.

★ Commerce Platform Accounting Add-On

Commerce platforms like Shopify partners or marketplace operators use Sync for Commerce to ship a native 'sync to QuickBooks' or 'sync to Xero' feature for merchants. The /config/sync/commerce/{commerceKey}/{accountingKey}/start endpoint launches the hosted flow and the /companies/{companyId}/connections endpoints manage the resulting connection lifecycle so merchants get reconciled accounting without manual exports.

Start a Sync for Commerce flow for company {companyId} with commerce key 'shopify' and accounting key 'quickbooksonline'.

Reseller and ISV Embedded Sync

ISVs and resellers embed Sync for Commerce inside vertical SaaS so their merchants can push sales to accounting without the ISV building the integration. The /config/integrations and /config/integrations/{platformKey}/branding endpoints let the ISV configure which platform pairs are exposed and apply their brand to the hosted flow.

List available integrations and update the branding for platform key 'shopify' so the hosted flow shows the partner logo.

Daily Sales Reconciliation

Multi-channel merchants use Sync for Commerce to write each day's gross sales, fees, refunds, and tax components into their accounting ledger as a single posted journal. The /companies/{companyId}/sync/commerce config endpoint controls cadence and mapping, and the standard sync endpoints monitor each run so the finance team knows the day's totals reconciled.

Trigger a sync for company {companyId} and monitor the run until it returns a final status.

AI Agent Onboarding Assistant

AI agents that onboard merchants to a Sync for Commerce experience use Jentic to drive the flow. The agent searches Jentic for 'start sync for commerce', loads the schema, and walks the merchant through commerce and accounting selection. Jentic isolates the Codat API key in its vault so the agent only handles the merchant-facing inputs.

Search Jentic for 'sync for commerce start', load the operation, and start the hosted flow for a Shopify merchant connecting to Xero.

Key Endpoints

22 endpoints — codat's sync for commerce api automates the daily push of commerce platform sales, fees, and refunds into a merchant's accounting software.

METHOD

PATH

DESCRIPTION

GET

/config/sync/commerce/{commerceKey}/{accountingKey}/start

Start the hosted Sync for Commerce flow

POST

/companies

Create a company record for a sync merchant

POST

/companies/{companyId}/connections

Create a connection for the merchant

POST

/companies/{companyId}/connections/{connectionId}/authorization

Authorize the accounting connection

GET

/config/companies/{companyId}/sync/commerce

Read the sync configuration for a merchant

GET

/config/integrations

List available commerce and accounting integrations

GET

/config/integrations/{platformKey}/branding

Get branding settings for a specific platform

GET

/config/sync/commerce/{commerceKey}/{accountingKey}/start

Start the hosted Sync for Commerce flow

POST

/companies

Create a company record for a sync merchant

POST

/companies/{companyId}/connections

Create a connection for the merchant

POST

/companies/{companyId}/connections/{connectionId}/authorization

Authorize the accounting connection

GET

/config/companies/{companyId}/sync/commerce

Read the sync configuration for a merchant

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Codat API keys are stored encrypted in the Jentic vault. Agents receive a scoped execution token; the 'Basic' Authorization header is constructed inside Jentic and never enters the agent runtime.

Intent-based discovery

Agents search Jentic by intent (e.g. 'sync commerce sales to accounting') and Jentic returns the matching Sync for Commerce operation with its input schema, so the agent does not have to navigate the 22 paths.

Time to first call

Direct Codat Sync for Commerce integration: 2-4 weeks for auth, hosted-flow embedding, and per-platform onboarding. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Codat Commerce API

Reads commerce orders and payments; Sync for Commerce writes them to accounting

Use Commerce when the agent needs to read merchant data; use Sync for Commerce when the agent needs to push commerce data into accounting platforms.

Alternative

Codat Sync for Expenses

Pushes expense transactions into accounting; Sync for Commerce pushes commerce sales

Choose Sync for Commerce for sales-side data; choose Sync for Expenses for expense-side data.

Complementary

Codat Accounting API

Provides full read and write access to the destination accounting ledger

Use Accounting when the agent needs full ledger control; use Sync for Commerce when the agent only needs the commerce-to-accounting sync flow.

FAQs

Specific to using Sync for Commerce API through Jentic.

What authentication does the Sync for Commerce API use?

The API uses an API key passed in the Authorization header as 'Basic <base64-encoded-key>'. The single security scheme in the spec is named auth_header. Through Jentic, the Codat API key is stored encrypted in the vault and the Authorization header is constructed inside Jentic, never reaching the agent.

Can I start a sync flow between Shopify and QuickBooks programmatically?

Yes. Call GET /config/sync/commerce/{commerceKey}/{accountingKey}/start with commerceKey='shopify' and accountingKey='quickbooksonline' to launch the hosted flow URL the merchant completes. After authorization the standard sync endpoints under /companies/{companyId} take over for ongoing runs.

What are the rate limits for the Sync for Commerce API?

Codat does not publish a fixed rate limit in the OpenAPI spec; limits are governed at the company and connection level and depend on the underlying commerce and accounting platforms. Codat returns HTTP 429 with a Retry-After header when limits are hit and recommends exponential backoff.

How do I list available platform pairs through Jentic?

Search Jentic for 'sync for commerce integrations', load the GET /config/integrations operation, and execute it. Install with pip install jentic and use the standard async search, load, and execute flow.

Can I brand the hosted Sync for Commerce flow for my partner integration?

Yes. Use the /config/integrations/{platformKey}/branding endpoint to apply your partner branding to the hosted onboarding flow. ISVs and resellers use this to keep the experience inside their own UI shell while Codat runs the underlying connection plumbing.