- Create and list orders; fetch the dealer product list
- Central warehouse (2890): product lookup, order creation and delivery status
- ESD licence information, warranty check and technical-service check
- No HTTP-level authentication: dealer code, user and password travel inside the envelope's auth block, assembled by Iris
- Atlas forwards the XML body as-is with the correct SOAPAction; test host webservistest.penta.com.tr for onboarding
- 9 catalogued routes, runnable from the Iris integrations hub behind a confirmation
Penta SOAP Web Service Connector
Penta Teknoloji's SOAP 1.1 web service at webservis.penta.com.tr — orders, products, central-warehouse (2890) stock, orders and deliveries, ESD licence data, warranty and technical-service checks — connected to Apivom Iris, which builds the full SOAP envelope with your dealer credentials inside and forwards it verbatim.
What you can do
Use cases
- Keep a legacy SOAP integration without the plumbing — Dealers whose processes were built on Penta's web service can run the same operations from Iris while the envelope, SOAPAction and credential handling are done for them.
- Warranty and service checks for support — Query warranty status and technical-service eligibility for a customer's product from their Iris record, with Penta's XML answer kept on the timeline.
- Central-warehouse orders from the deal — Look up 2890 availability, create the warehouse order and follow its delivery from the opportunity.
Alongside its JSON APIs, Penta Teknoloji still operates a SOAP 1.1 web service at webservis.penta.com.tr that many dealer ERPs were integrated with first. Its nine operations mirror the REST service: create and list orders, read the product list, look up central-warehouse (2890) products, create warehouse orders and track their delivery, retrieve ESD licence information, and check warranty and technical-service status. The protocol is the difference: there is no HTTP authentication at all — the dealer code, user and password are carried inside an auth block of the SOAP envelope. Apivom Iris therefore assembles the complete XML envelope for each call, including the credentials stored encrypted in your tenant, and Apivom Atlas forwards that body verbatim to Penta with the SOAPAction header the operation requires, then logs request and response in your tenant. Nothing is stored in Atlas. Because every operation is a SOAP POST, the routes run from the Iris integrations hub behind an explicit confirmation step, and Penta's test host lets a dealer validate the envelopes against a test account before production.
No HTTP auth. Iris embeds your dealer code, user and password in the <auth> block of each SOAP envelope and sends the whole envelope as the request body; Apivom Atlas forwards it verbatim with the right SOAPAction and logs the call. Credentials stay encrypted in your Iris tenant.
Frequently asked questions
How are my credentials protected if there is no HTTP authentication?
They are stored encrypted in your Iris tenant and inserted into the SOAP envelope by Iris at call time. Apivom Atlas receives the finished envelope, forwards it over TLS to Penta and logs the call; it never holds the credentials separately.
Should I use the SOAP or the REST connector?
They cover the same dealer operations. Use REST for new work; the SOAP connector exists for dealers whose Penta processes and reference data are already aligned with the web service.
Does Apivom charge per API call for this connector?
No. Connectors are part of your Apivom tenant and are not metered in the Atlas portal. The vendor's own pricing, quotas and rate limits still apply to the account you connect — Apivom paces its calls to stay inside them and shows every call in your tenant's integration log.
Where are my credentials stored and who can see the traffic?
Apivom Atlas is a stateless gateway: it never stores vendor credentials or tokens. The Apivom product that connects keeps the credential encrypted in your tenant database, and every request and response is logged in your tenant only — your data is never shared across tenants.
More Atlas integrations
AI integration guide (llms.txt)
Machine-readable markdown — feed it to your AI assistant as integration instructions.