- Create an order and query its status; list products available to the dealer
- Central warehouse (2890): product availability, order creation and delivery tracking
- ESD licence information for electronically delivered software
- Warranty check and technical-service check for a serial number or product
- 12-hour Bearer token acquired by Iris from /api/Auth/RequestToken and cached; separate test host (apiresttst.penta.com.tr)
- 9 catalogued routes, runnable from the Iris integrations hub behind a confirmation
Penta REST API Connector
Penta Teknoloji's REST API at apirest.penta.com.tr — product lists, order create and query, central-warehouse (2890) stock, orders and deliveries, ESD licence information, warranty and technical-service checks — connected to Apivom Iris with your dealer credentials and a 12-hour token Iris obtains itself.
What you can do
Use cases
- Warranty answers on the first call — Run the warranty and technical-service checks for a customer's serial number from their Iris record while they are on the phone.
- Central-warehouse orders with delivery tracking — Check 2890 stock for the items on a deal, create the warehouse order and follow the delivery status from the same opportunity.
- Licence keys for software you sold — Pull ESD licence information for an electronically delivered product and keep it with the customer's purchase history.
Penta Teknoloji's REST API is the lighter, JSON-based dealer service that sits beside the Base API and the SOAP web service. Its nine operations cover the daily questions a reseller asks its distributor: which products can I buy, is it in the central warehouse (Penta's 2890 location), create an order there and follow its delivery, what is the licence information for an ESD product I sold, and is this serial still under warranty or eligible for technical service. Apivom Iris connects with the dealer's customer code, user and password; Penta issues a 12-hour token from /api/Auth/RequestToken, which Iris requests directly from Penta, caches and attaches as a Bearer header to each call forwarded through Apivom Atlas — the password never leaves your tenant and the token routes are intentionally outside the catalogue. All routes are POST operations, so they run from the Iris integrations hub behind a confirmation, with request and response logged in your tenant. Penta's test host lets a new dealer verify the whole flow before production.
Dealer code (customer) + user name + password. Iris calls Penta's /api/Auth/RequestToken directly, caches the 12-hour token and sends it as Bearer per request; the token routes are deliberately not registered. The password stays encrypted in your Iris tenant; Apivom Atlas stores nothing.
Frequently asked questions
Why are there three Penta connectors?
Penta exposes three services with different scopes and protocols: the Dijital microservice (catalogue, standard orders, subscriptions), the Base API (production orders) and this REST API (central-warehouse orders, licences, warranty). Each is registered separately so the credential, host and routes stay exact.
How is the token refreshed?
Iris requests a new 12-hour token from Penta's /api/Auth/RequestToken when the cached one expires, using the dealer credentials stored encrypted in your tenant. Apivom Atlas only ever forwards the resulting Bearer header.
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.