- Production orders: create, read, list and delete; attach documents to an order; component-service operations
- Project list for the dealer account — the price-project context Penta applies to orders
- 12-hour token acquired by Iris straight from Penta's token endpoint and reused until it expires
- Separate test host (apitest.penta.com.tr) for onboarding; 7 catalogued routes
- Every call runnable from the Iris integrations hub behind a confirmation, logged in your tenant
Penta Base API Connector
Penta Teknoloji's Base API at api.penta.com.tr — production orders, order documents, component services and project lists for dealers — connected to Apivom Iris with your dealer code, user and password: Iris obtains the 12-hour token directly from Penta and caches it.
What you can do
Use cases
- Configured-system orders from the deal — Place a production order for a configured server, workstation or kit from the opportunity and attach the customer's order document in the same step.
- Follow production from the CRM — Read and list production orders onto the customer record so account managers can answer where a build stands without opening the dealer portal.
- Right project, right price — Fetch the dealer's project list and pick the project that applies before an order is created, so pricing matches what Penta will invoice.
Penta Base API is the dealer-facing service of Penta Teknoloji at api.penta.com.tr. Where the Penta Dijital microservice covers the catalogue and standard orders, the Base API addresses production orders — orders that Penta assembles or configures before shipping: create a production order, read or list existing ones, delete a draft, attach order documents, call the production component service, and fetch the dealer's project list that defines the pricing context. Apivom Iris connects to it with the dealer's own customer code, user and password. Because Penta issues its own 12-hour token, Iris performs the token call directly against Penta, caches the token until it expires and forwards only the resulting Bearer header through Apivom Atlas — the password is never sent to Atlas and nothing is stored there. All seven routes are write-style POST operations, so they run from the Iris integrations hub behind an explicit confirmation step, with request and response logged in your tenant. Penta's test host lets you validate the flow with a test dealer account before production.
Dealer code (customer) + user name + password from your Penta account. Iris calls Penta's token endpoint directly, receives a token valid for 12 hours plus a refresh token, caches it and sends it as Bearer per request. The password stays encrypted in your Iris tenant; Apivom Atlas stores nothing.
Frequently asked questions
How is the Penta token handled?
Iris calls POST /Token/NewToken on Penta with your dealer code, user and password, receives a 12-hour token and a refresh token, caches them in your tenant and attaches the Bearer token to each call. The token routes themselves are not proxied, so credentials never pass through Apivom Atlas.
Are these the same orders as in Penta Dijital?
No. The Base API covers production (configured) orders and their documents; standard catalogue orders, stock and subscriptions live in the Penta Dijital microservice API, which Apivom registers as a separate connector.
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.