Integrator for Divalto
Integrating the Divalto API into your system
We wire Divalto Infinity into your ecommerce, jobsite app, or portal: the order creates the document, stock and price stay the ERP's. No double entry, no parallel spreadsheet.
- Senior product team
- ERP connectors in production
- scoping through to monitoring
Why work with a Divalto integrator and what can be connected to Divalto Infinity?
Divalto Infinity is an ERP for industrial and distribution SMEs, common in construction, trade and services. You integrate it so your ecommerce, jobsite app or portal live on it: a site order becomes a document, ERP stock and price show online, a jobsite work order is invoiced, outstanding balance without Excel. Infinity stays the system of record; we connect around it, we do not replace it. Every project starts by clarifying the version, modules and write channel with your Harmony partner, because Divalto does not expose a standard REST API.
What Divalto changes in your platform
Ecommerce order created in Infinity
The site creates the sales document. Stock, price, VAT and dunning stay the ERP's, not a storefront duplicate.
ERP stock and price on the site
Availability and price shown are Infinity's. You sell what you have, without a parallel stock spreadsheet.
Jobsite work order becomes a sales document
On close-out, the work order is created in Infinity. Field teams keep their tool, commercial management stays in the ERP.
Customer balance without a parallel spreadsheet
The customer sees their orders and outstanding balance in the portal. No heavy Harmony client, no shared sales-admin file.
What it changes in your product
Engineering in service of a measurable outcome: site orders in Infinity, ERP prices, a reliable balance.
Infinity stays the source of truth
Document, stock and price live in the ERP. Your site or app attaches to it, it does not reinvent commercial management.
Your teams keep Harmony
Sales and order desk stay in Divalto. Nobody has to change screens for the ecommerce flow to exist.
The CRM-ERP bridge already in place, we leave it
If Harmony and Infinity are already linked, we do not rewrite that bridge. We wire the third system (site, jobsite, portal) around it.
A connector that belongs to you
Code delivered, documented, logged for Diva support. We work with your Harmony reseller, without a black box.
How we wire Divalto into your platform
Scoping
Where Infinity enters your product: ecommerce, jobsite, portal. Cloud or on-premises, version, weavy, actions already configured. On-premises: agent or VPN, never port 8080 opened as-is.
SW inventory
List of swinfinity actions and custom Diva programs. We do not rewrite a5ppswinfinity.dhop without the partner. Mapping of parties, items, documents.
Development and testing
A connector wired into your site, jobsite app or portal. JSON RPC layer, token out of logs, idempotency. Testing on the named environment.
Monitoring
Log of param and response (secrets excluded) for Divalto support. You see an incident before it breaks the channel or invoicing.
What the API brings to your platform
- Create the document from the channel
- WEB_SERVICE_INFINITY writes the order, customer or item via a Harmony action. Each action has its contract: that is the write channel for the site or jobsite.
- Read stock and balance for the portal
- Cloud OData or business interrogation as read-only. Enough to power the portal or a BI cube, without writing into the ERP.
- Extract without a business program
- RecordSQL reads via Harmony SQL objects. Useful for a portal, not for ERP entry rules.
- Keep weavy already in place
- The weavy to Infinity kit covers customers, contacts, items, history. Specific work sits on the third system.
The vocabulary of a Divalto integration
- WEB_SERVICE_INFINITY
- The REST write channel: one Harmony action, one Diva program (a5ppswinfinity.dhop by default). Each business action (swinfinity) has its own JSON contract.
- swinfinity
- The business action name in the param field (INTERROGER, plus sales, production, project actions). Not a REST HTTP verb.
- $webservice
- The technical ERP user that carries rights and implicits. It must exist on every Cloud environment. It is not a salesperson's login.
- Cloud OData
- Read-only on odata.one.divalto.com. SaaS licence to subscribe, ERP project code created on request. Physical names, SQL-visible fields only.
- weavy
- Divalto CRM. The kit to Infinity covers customers, contacts, items, history. It is not the open API of a third-party SaaS.
- Harmony
- The Divalto runtime (thick client, SW actions, $webservice user). Support diagnoses in Diva, not in semantic HTTP codes.
The real constraints of a Divalto integration
This is not a resource REST API
WEB_SERVICE_INFINITY is JSON RPC around Diva programs. No public OpenAPI comparable to a SaaS. Each swinfinity action has its contract, to inventory with the partner.
OData Cloud cannot write into the ERP
Promising two-way sync « via Divalto OData » is false. Writes go through WEB_SERVICE_INFINITY, a file import, or the kit. OData is BI.
The token travels in the body
Middleware that injects Authorization Bearer is not enough. A proxy that logs the body logs the secret. Cache the token, never in the logs.
On-premises and Cloud do not wire the same way
On-premises: HTTP by default, port 8080, VPN or agent. Cloud: api.divaltocloud.com/{site}/{env}. A public SaaS does not hit a local Infinity without a controlled exposure.
Write into Infinity or read via OData
Two channels, two licences, two uses. Mixing them in a quote produces a false connector on the first write flow.
| Criterion | WEB_SERVICE_INFINITYERP writes | Cloud ODataRead-only |
|---|---|---|
| Direction | Writes (and business interrogation) | Read-only |
| Protocol | JSON RPC, Execute, token in the body | OData, Basic auth, physical tables |
| Host | On-premises port 8080, or api.divaltocloud.com/{site}/{env} | odata.one.divalto.com/odata |
| Prerequisites | $webservice user, Harmony actions configured | OData SaaS licence, weavy ≥ 5, infinity ≥ 10 |
| Model exposed | swinfinity contracts, Diva programs | Physical names, SQL-visible fields, no TEXT/BLOB |
| The right case | Ecommerce, portal, jobsite app that creates the document | Power BI, Excel, margin and balance reporting |
| What it is not | Not a resource REST API with a public OpenAPI | Not CRUD, not two-way sync |
We claim no Divalto partnership or certification. We build on the documented web services, with the client's Harmony reseller.
What we measure on a Divalto project
The other ERPs we integrate
The choice follows whichever ERP you already run, rarely the technology.
DivaltoIntegrating the Divalto API into your systemThis page
OdooOpen ERP: API over the whole object model, Python modules if needed.
SAPS/4HANA Cloud on published OData, BTP beside it, not a single API.
Microsoft DynamicsSales in Dataverse, Finance in F&O, SMEs in Business Central.We combine Divalto with
The stack that surrounds Infinity and weavy on our projects.
Divalto integration: your questions
First map where Infinity enters your product (ecommerce, jobsite, portal) and the hosting: Cloud or on-premises. Writes go through WEB_SERVICE_INFINITY: authentication, token in the JSON, then Execute with the business action. For a read portal, business interrogation or Cloud OData depending on the licence. Idempotency on the caller side (document number, party code). We inventory actions already configured at the partner. The real difficulty is not the RPC, it is that the site order and the stock shown share the same Infinity truth.
It depends on the touchpoints, the access channel and the hosting. Ecommerce that pushes orders is priced differently from an orders-and-balance portal plus a BI cube. Two things weigh heavily: on-premises (exposure, certificate, agent) and the OData SaaS licence, created on request. Custom Diva programs lengthen the inventory. We scope hosting and actions, then give a firm estimate.
No. Cloud OData is explicitly read-only: Basic auth, per-table « read » API account, physical names, no TEXT/BLOB. It is a BI channel (Power BI, Excel), not CRUD. Writes (sales document, customer, item) go through WEB_SERVICE_INFINITY, possibly a file import or the weavy kit. Two-way sync « via OData » is a false quote. If the need is to write, we start from the REST SW, full stop, and we inventory the swinfinity actions with the Harmony partner first.
The Harmony reseller is useful for ERP configuration, implicits, SW actions and the OData licence. For a connector to a SaaS or an ecommerce site, what counts is command of the JSON RPC, of the token in the body, and the ability to log for a Diva diagnosis. We claim no Divalto partnership: we build on the documented web services, and we work with the Harmony partner already running your Infinity. That split keeps ERP parameterization where it belongs.
The business action is the same (Execute, swinfinity), the URL and the exposure change. Cloud: https://api.divaltocloud.com/{NUMEROSITE}/{ENVIRONNEMENT}/api/v1/, $webservice to create on every environment. On-premises: http://{host}:8080/DhsDivaltoServiceDivaApiRest/api/v1/WebService/Execute, HTTP by default, HTTPS only if a certificate is installed. A public SaaS does not talk to a local Infinity without VPN, an agent or a controlled exposure. Read OData is a Cloud service (odata.one.divalto.com), with a dedicated licence, distinct from the write SW.
A Divalto integration project?
Let's talk. 30 minutes to identify where Infinity touches your channel or jobsite, Cloud or on-premises, the actions already open, then tell you honestly what is feasible.
Discuss my Divalto project