Codat Sync for Expenses API

Can I push corporate card transactions into QuickBooks with this API?

Yes. After creating a partner-expense connection via /companies/{companyId}/sync/expenses/connections/partnerExpense, push expenses through the sync endpoints under /companies/{companyId}/sync/expenses. The transactions arrive in QuickBooks with the GL account, tax rate, and tracking category applied based on the mapping options you supply.

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

How do I check why an expense transaction failed to post through Jentic?

Search Jentic for 'expense sync transaction status', load the GET /companies/{companyId}/sync/expenses/syncs/{syncId}/status operation, and execute it with the sync ID. Install with pip install jentic and use the standard async search, load, and execute flow.

Which accounting platforms does Sync for Expenses support?

Sync for Expenses supports QuickBooks Online, Xero, and Sage as primary destinations using the same endpoint surface. The destination is selected when the partner-expense connection is created, and the mapping options endpoint returns the destination-specific chart of accounts.

Note that the API spec marks this API version as 'prealpha' - is it production-ready?

The OpenAPI spec exposes version 'prealpha' in info.version, indicating Codat may still iterate on the surface. Production deployments should pin to the spec version they tested against and watch for breaking changes; through Jentic the loaded schema is versioned with the spec used at search time.

Can I limit what my agent is allowed to do with the Sync for Expenses API?

Yes. Because you run Jentic One yourself, your own rules decide which Sync for Expenses operations the agent may call and which Codat credentials it may use. Since the company id sits in the URL path (/companies/{companyId}/sync/expenses/...), you can pin the agent to a single company and give it read-only access to that company's sync configuration, mapping options, and sync status. Triggering a new expense sync via POST /companies/{companyId}/sync/expenses/syncs is only in the allowed set if you add it, so the agent cannot post to the ledger unless you grant that operation.