- Full product list as XML (liste-genel-xml): the dealer catalogue with prices and availability as Penta publishes it
- Per-product detail feed (urun-detay) for descriptions, attributes and images
- No HTTP credential: Penta allow-lists one caller IP per dealer; your dealer code travels as the Customer query parameter
- Both routes are read-only; Penta limits pull frequency (standard interval about 60 minutes)
- Responses are XML and are passed through as text, ready for your import tooling
Penta XML Product Feed (Bayinet) Connector
Penta Teknoloji's XML product integration services on Bayinet — the full dealer product list and per-product detail as XML feeds — registered in Apivom Atlas for resellers that publish Penta's catalogue to their own shop or ERP. Access is by IP allow-list, not by credential.
What you can do
Use cases
- Publish the distributor catalogue in your shop — Pull the hourly product list and refresh prices and availability in your e-commerce platform without manual spreadsheet uploads.
- Enrich product pages — Fetch the detail feed for the products you list to add descriptions, attributes and images sourced from Penta.
- Catalogue data for your ERP — Feed item master data from the XML list into your ERP so purchasing and sales work from the same Penta article numbers.
Bayinet is Penta Teknoloji's dealer portal, and its XML product integration services are the classic way a reseller mirrors the distributor's catalogue into an e-commerce site or ERP: one feed returns the complete product list with prices and stock as Penta publishes it, the other the detail of a single product. Apivom Atlas registers both routes so that Apivom tenants can pull the feeds through the gateway with per-tenant logging and the published AI integration guide (llms.txt). The access model is unusual: Penta issues no API key but allow-lists a single caller IP address per dealer, and the dealer identifies itself with its customer code in the Customer query parameter — so the gateway's egress address must be the one registered at Penta. Penta also caps how often the list may be pulled, roughly once an hour under the standard agreement, so a scheduled hourly import is the intended pattern. Both routes are read-only and return XML, which Atlas passes through as text. No Apivom product workflow consumes this feed today; it is registered for tenants who want to drive their own catalogue import from it.
IP allow-listing on Penta's side (one caller IP per dealer) plus your dealer code as the Customer query parameter on each request — there is no HTTP credential. Apivom Atlas stores nothing; its egress address must be registered with Penta for the feed to answer.
Frequently asked questions
Can I switch this connector on today?
The connector is registered in Apivom Atlas — every route is catalogued, the credential contract is published and the AI integration guide (llms.txt) is live — and your credential can be stored in Apivom Iris. Wiring it into a product workflow (sync, automation, notifications) is done per customer: tell us the use case and we scope it with you.
How does access work if there is no API key?
Penta allow-lists one caller IP address per dealer and expects your dealer code as the Customer query parameter. Through Apivom Atlas, the gateway's egress IP is the address that has to be registered with Penta; until it is, the feed will not answer.
How often can the feed be pulled?
Penta limits the pull frequency — about once every 60 minutes under the standard arrangement. Design your import as a scheduled hourly job rather than on-demand calls.
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.