- Create a Penta order from an Iris opportunity: the user reviews and approves every line before anything is sent
- Simulate-or-update first, create second — price and availability are confirmed by Penta before the real order
- Read order status and order lists; cancel an order from the same screen
- Products, brands, categories, project lists and outlet stock from the catalogue routes; subscriptions and end users for licence resale
- Scheduled catalogue and order reads by Apivom Staff; staging (test) service available for onboarding
- 28 catalogued routes (12 read-only), tryable from the Iris integrations hub
Penta Dijital Dealer API Connector
Penta Teknoloji's dealer (bayi) microservice API — products, stock and prices, orders, subscriptions and end users — connected to Apivom Iris and Apivom Staff: build a Penta order from an opportunity, simulate it, submit it after approval and read its status, with your own portal token.
What you can do
Use cases
- Won deal → distributor order in minutes — Turn the approved lines of an opportunity into a Penta order, simulate it, fix what Penta flags and submit — without re-keying anything into the dealer portal.
- Quote with live stock and dealer price — Check outlet stock and project price lists for the products on a quote so the price you commit to is the one Penta will confirm.
- Cloud licence lifecycle for end customers — Add, renew, increase, decrease or cancel subscription products for an end user from the customer's record and keep the subscription list in sync.
- Order tracking on the customer timeline — Read order status and history onto the opportunity so sales and operations see the same fulfilment state.
Penta Teknoloji is one of Türkiye's largest IT distributors, and Penta Dijital is its dealer platform. Its microservice API lets a reseller work with the distributor programmatically: product catalogue with brands and categories, outlet stock and project price lists, order creation, simulation, update and cancellation, order history, and — for cloud licence resale — subscriptions, end users and the add/renew/increase/decrease/cancel operations on them. Apivom Iris connects as a dealer: when an opportunity is won, the account manager assembles a Penta order from its lines, runs Penta's simulate step to confirm prices and stock, reviews the answer and only then approves the real submission — nothing reaches Penta without that explicit confirmation. Order status and history are read back onto the opportunity, and Apivom Staff runs the scheduled reads (catalogue, orders) so the data is fresh when someone opens the record. The credential is the dealer's own portal token; Penta's staging service lets a new dealer test the whole flow before switching to production. Every request and Penta's response are logged in your tenant.
Portal token from Penta Dijital (Yönetim → Konfigürasyon), sent raw in the Authorization header on every call — no Bearer prefix. Iris keeps it encrypted in your tenant; Apivom Atlas forwards and logs the call without storing the token. A staging host exists for test accounts.
Frequently asked questions
Can an order be sent to Penta by mistake?
No. The flow is simulate first, then an explicit review-and-approve step by the user; only that approval triggers the real create-order call. Writes run from the hub also sit behind a confirmation, and every call is logged.
Which Penta data is refreshed automatically?
Apivom Staff runs scheduled reads of the product catalogue and of orders so lists and statuses are current when a record is opened. Order creation, updates and cancellations are always user-initiated.
Is there a test environment?
Yes. Penta Dijital provides a staging microservice host; connect a staging token first, run the full order flow against it, then switch the credential to production.
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.