What API2Cart Is Evaluating for xTuple ERP Integration
Candidate workflow
Connect digital orders with customers, items, sales orders, inventory, purchasing, and production. Final entity and method coverage will follow verified vendor interfaces and customer requirements.
Operational outcome
The intended result is to preserve site, warehouse, unit, lot, serial, tax, and document-status relationships. Identity rules and idempotency would be defined before transactional writes are enabled.
ERP safeguards
The design must support open deployment choices while maintaining idempotent transactional synchronization. Customers, products, sales orders, fulfillments, invoices, and production records would keep their distinct lifecycle roles.
Develop Integrations Faster and Save Up to 9x on Costs
Trusted by
What We Know About xTuple ERP So Far
Based on xTuple ERP’s own documentation and API2Cart’s discovery process — not a promise of a release date.
API & Integration. xTuple exposes a REST API supporting standard GET/POST/PATCH/DELETE operations, authenticated via OAuth 2.0 through a "Services Account" client registered in xTuple's OAuth2 interface. Public developer documentation is sparse and, per xTuple's own references, still being migrated to GitHub, so integrators should expect to rely on the Programmer Reference and community client examples rather than one canonical, current API spec. No published rate limits, sandbox environment, or API versioning scheme could be verified.
xTuple ERP integration is not live yet. Authentication, modules, entities, fields, writes, events, limits, editions, and release timing remain subject to technical discovery and demand.
Background. xTuple developed from the PostBooks open-source ERP lineage and built commercial editions for manufacturing and distribution. Archived xTuple material described the company as a long-established ERP vendor by 2018; current product stewardship and packaging must be verified because ownership, editions, and supported delivery channels have changed over time.
Where it specializes. xTuple has been used by small and midsize manufacturers and distributors for sales, purchasing, inventory, bills of material, work orders, scheduling, costing, accounting, and customer management. Its manufacturing context can include make-to-stock, make-to-order, and engineer-to-order operations, so item sites, warehouses, revisions, routings, work orders, and costing methods matter.
Integration challenge. xTuple deployments have offered a PostgreSQL-backed application, desktop and web clients, and REST-style web services for third-party integration. However, an “xTuple” installation may be PostBooks, a commercial edition, a customized legacy release, or a newer solution managed by a different provider. Discovery must identify ownership and support status, exact edition and version, enabled web-service layer, authentication, schema extensions, database privileges, and supported write methods. Direct database access should not be treated as a safe replacement for business-level APIs.
Technical validation. Engineering must verify edition, REST services, authentication, custom schema, and extension compatibility. Unsupported modules and operations would remain outside the public scope.
Roadmap evaluation considers API maturity, sandbox access, operational correctness, commerce relevance, scale, customer demand, maintenance cost, deployment variants, and overlap with existing connectors. This page records a candidate, not a promised release date.
Primary sources: Archived xTuple product and company material · xTuple manufacturing and finance guide · Current xTuple ERP product sheet
Related planned integrations: metasfresh integration · Tryton integration · ADempiere integration · Oracle Fusion Cloud ERP integration
Interested in xTuple ERP Integration?
Let us know you’re interested, and we’ll notify you as soon as xTuple ERP support becomes available.
