Codat Commerce API

Name: Commerce API
Brand: Commerce API
Availability: InStock

✓ Official Vendor SpecE CommerceOrder ManagementapiKey21 EndpointsREST

Install Jentic One Beta

Connect the Commerce API to your agent

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

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: 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

Step 2: 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 Commerce API.

Retrieve orders with line items, totals, taxes, and customer references from connected commerce platforms

Read payment records and transactions tied to orders for payout reconciliation

List customers and customer profiles linked to commerce orders

GET STARTED

Start building with Commerce API

Explore with Jentic

View OpenAPI Document

For Agents

Read normalised orders, payments, products, customers, and disputes from a merchant's connected commerce platform such as Shopify, Square, Stripe, or Amazon.

Use for: I want to list a merchant's orders from Shopify or Square, Get the payment record attached to a specific commerce order, Find all disputes filed against a merchant in the last 30 days, Retrieve product catalogue data for a connected store

Not supported: Does not handle writing commerce data, accounting ledger access, or payment processing - use for reading normalised orders, payments, products, and disputes from connected commerce platforms only.

Use Cases

Patterns agents use Commerce API for, with concrete tasks.

★ Revenue-Based Lending Diligence

Capital providers offering revenue-based finance use the Commerce API to verify a merchant's order volume and payment history. The /companies/{companyId}/connections/{connectionId}/data/commerce-orders, /commerce-payments, and /commerce-transactions endpoints provide the trailing volume series the underwriting model needs, normalised across Shopify, Square, Stripe, and Amazon so one integration covers every applicant.

Fetch the last 12 months of commerce-orders for company {companyId} connection {connectionId} and compute monthly gross merchandise volume.

Payout Reconciliation

Finance teams at multi-channel merchants reconcile platform payouts using the Commerce API's payments and transactions endpoints. The /commerce-payments and /commerce-transactions data ties each settled amount back to the originating order so the team can match payout deposits in the bank to the gross order plus fees and refunds reported by the commerce platform.

List commerce-payments for company {companyId} for the last week and group them by order ID to support payout matching.

Multi-Channel Merchant Analytics

B2B SaaS products serving multi-channel sellers use the Commerce API to build a unified analytics view across Shopify, Amazon, eBay, and Square. The same /commerce-orders, /commerce-products, and /commerce-customers endpoints work regardless of source, eliminating the per-platform connector work that historically blocked these products from launching with broad coverage.

Pull product catalogue and last-30-day order data for company {companyId} across all connections and compute revenue per SKU.

AI Agent Merchant Insights

AI agents that surface merchant-specific insights use the Commerce API through Jentic. The agent searches Jentic for 'list commerce orders', loads the schema, and pulls trailing orders and disputes for a merchant. Jentic isolates the Codat API key in its vault and the unified search means the agent does not have to know the Codat path naming scheme.

Search Jentic for 'commerce disputes codat', load the operation, and list every open dispute for company {companyId} with reason and amount.

Key Endpoints

21 endpoints — codat's commerce api exposes a unified read interface for orders, payments, customers, products, locations, disputes, transactions, and tax components from a customer's connected commerce platform.

METHOD

PATH

DESCRIPTION

GET

/companies/{companyId}/connections/{connectionId}/data/commerce-orders

List commerce orders from a connected platform

GET

/companies/{companyId}/connections/{connectionId}/data/commerce-payments

List commerce payments

GET

/companies/{companyId}/connections/{connectionId}/data/commerce-transactions

List underlying commerce transactions

GET

/companies/{companyId}/connections/{connectionId}/data/commerce-customers

List commerce customers

GET

/companies/{companyId}/connections/{connectionId}/data/commerce-products

List products in the connected catalogue

GET

/companies/{companyId}/connections/{connectionId}/data/commerce-disputes

List disputes and chargebacks

GET

/companies/{companyId}/connections/{connectionId}/data/commerce-orders

List commerce orders from a connected platform

GET

/companies/{companyId}/connections/{connectionId}/data/commerce-payments

List commerce payments

GET

/companies/{companyId}/connections/{connectionId}/data/commerce-transactions

List underlying commerce transactions

GET

/companies/{companyId}/connections/{connectionId}/data/commerce-customers

List commerce customers

GET

/companies/{companyId}/connections/{connectionId}/data/commerce-products

List products in the connected catalogue

Why Jentic?

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

Credential isolation

Your Codat API key is stored once, encrypted, by your own Jentic One instance and injected at execution time as the Basic Authorization header. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list commerce orders for a merchant' or 'read commerce payment disputes', and Jentic returns the matching Commerce operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using Commerce API through Jentic.

What authentication does the Codat 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 never enters the agent context - Jentic injects the Authorization header at execution time.

Can I read Shopify and Stripe order data with the Codat Commerce API?

Yes. The /companies/{companyId}/connections/{connectionId}/data/commerce-orders endpoint returns orders normalised across Shopify, Stripe, Square, Amazon, eBay, and other supported commerce platforms, so the same call works regardless of which platform the merchant uses.

What are the rate limits for the Codat 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 platform's own limits. Codat returns HTTP 429 with a Retry-After header when limits are hit and recommends exponential backoff for retries.

How do I pull dispute records through Jentic?

Search Jentic for 'commerce disputes codat', load the GET /companies/{companyId}/connections/{connectionId}/data/commerce-disputes operation, and execute it with the company and connection IDs. Install with pip install jentic and use the standard async search, load, and execute flow.

Does the Codat Commerce API support write operations?

No. The Commerce API is read-only - it surfaces orders, payments, customers, products, and disputes from the connected platform. To push data back into accounting platforms use the Codat Sync for Commerce or Accounting API instead.

Can I limit what my agent is allowed to do with the Codat Commerce API?

Yes. Because you run Jentic One yourself, your own rules decide which Commerce operations the agent may call and which credentials it may use. Since Commerce puts the company id in the URL path, a rule can pin the agent to a single merchant, and because the API is read-only you can allow just the reads you want, such as orders and payments while excluding customers, products, or disputes. Your Codat API key stays with your instance and is injected only when an allowed call runs.