What API2Cart Is Evaluating for Dolibarr Integration
Candidate data flow
Commerce data connected with third parties, products, orders, and invoices. The final entity and method list will be based on verified vendor API capabilities rather than assumptions.
Operational outcome
The intended workflow is to work across self-hosted installations with different enabled modules. Record ownership and idempotency would be defined before write operations are enabled.
Accounting safeguards
The connector would need to avoid assumptions about custom fields and localized accounting configuration. Orders, invoices, payments, refunds, settlements, and journal entries would not be treated as interchangeable records.
Develop Integrations Faster and Save Up to 9x on Costs
Trusted by
What We Know About Dolibarr So Far
Based on Dolibarr’s own documentation and API2Cart’s discovery process — not a promise of a release date.
API & Integration. Dolibarr provides a REST API (JSON) that must be explicitly enabled via its "API REST" module before use, with a built-in Swagger/OpenAPI explorer at /api/index.php/explorer for testing endpoints. Authentication uses a per-user API key sent via the DOLAPIKEY header (or api_key query parameter), not OAuth or session cookies. Being self-hosted, there's no vendor-run sandbox, but multi-company installations are supported through a DOLAPIENTITY header that scopes each request to a specific entity when the Multi-Company module is active.
Is this integration live yet? No. Dolibarr integration is not live yet. Authentication, entities, fields, write operations, webhooks, limits, regional availability, and release timing remain subject to technical discovery and customer demand.
What’s the integration challenge? Engineering discovery must validate REST module status, API keys, entity support, and deployment version. Unsupported objects or operations would remain outside the published scope.
How is a release decided? Roadmap evaluation includes API maturity, sandbox access, accounting correctness, customer demand, maintenance cost, data residency, rate limits, and overlap with existing connectors. The page records an integration candidate; it does not promise a release date.
Technical validation. Engineering discovery must validate REST module status, API keys, entity support, and deployment version. Unsupported objects or operations would remain outside the published scope.
Primary sources: Official history or company background · Dolibarr official website · Official developer or product documentation
Related planned integrations: LedgerSMB integration · TallyPrime integration · BUSY Accounting integration · Vyapar integration
Interested in Dolibarr Integration?
Let us know you’re interested, and we’ll notify you as soon as Dolibarr support becomes available.
