Add-on Module
API Access and Product Integration Between Delbig Accounts
An add-on module for teams that want to expose Delbig data through a secure API, review ready-made integration options, or share permitted product data between companies that use Delbig.
4,750 TL / yr + VAT
Added to the main package
Short Answer
What is the Delbig API / Integration module?
This module separates three needs clearly: authorized access to Delbig data through API documentation, external connections through ready-made integration modules, and permission-based product/price/catalog sharing between two Delbig accounts. It does not mean that every external system is connected automatically; the scope depends on the target system, data direction and whether a ready integration exists.
Delbig API documentation
Quotes, orders, customers, products and similar data can be exposed to external systems with the required permission scope.
Ready integration modules
Connections such as Mikro, Logo, Parasut, Shopify or WordPress can be activated separately when they are published as ready modules.
Product sharing between Delbig accounts
A source company can share permitted products, visuals, prices or catalog fields with a dealer, sub-store or another Delbig account.
Not required for every company
If your workflow stays inside Delbig and there is no data exchange need, this module is not required.
Delbig-to-Delbig Integration
The main company manages products; dealers or sub-stores receive only permitted data
A manufacturer, distributor or main company using Delbig can define its products as a source for another Delbig account. The receiving side only gets the allowed product, image, price or catalog fields and continues its own sales workflow without entering the same data again.
- The source company decides which products and which fields are shared.
- The receiving account can use automatic sync or a manual approval flow.
- Product images, prices, catalog data and product changes can update according to permissions.
Integration Problem
Every integration is different; data direction and responsibility must be clear first
One company may only want to pull Delbig quote and order data into a reporting system. Another may need a ready connection with Parasut, Logo or another external tool. A manufacturer may want to share product catalog data with dealers that also use Delbig.
For that reason, API / Integration should not be described as simply “connected to your website”. API-out, API-in, ready integrations and Delbig-to-Delbig product sharing are different scenarios.
Module Scope
What does the API / Integration module include?
The page is positioned around Delbig API access, integration permissions, ready-made connection logic and permission-based product sharing between Delbig accounts. If a third-party connection is not available as a ready module, it is scoped as a separate project.
API documentation and access
Quotes, orders, customers, products and similar Delbig data can be accessed through authorized API flows.
Client, scope and security
API client, permission scope, secret rotation and revocation keep the connection under control.
Ready integration logic
Mikro, Logo, Parasut, Shopify or WordPress connections can be selected separately when published as ready modules.
Delbig-to-Delbig product source
One Delbig account can act as a product source for another Delbig account, with only allowed fields shared.
Product and field permissions
Policies can define priced or price-free, with images or without images, all products or selected product groups.
Automatic or manual sync
The receiving company can accept updates automatically or use an approval-based manual integration model.
Error and process logs
Successful, pending, ignored or failed sync records can be logged for review.
Custom connection scope
If no ready module exists, third-party adaptation is scoped separately and should not be assumed inside the module fee.
Integration Map
This module separates three different connection needs
Instead of showing generic operations screens on the API / Integration page, the important visual distinction is API access, ready connectors and permission-based product sharing between Delbig accounts.
Open Delbig data outward
Authorized systems use Delbig data through the API.
- API documentation and client information
- Scope, token, security and logs
- Quote, order, customer and product data
Enable it when the module exists
Every external system is not scoped the same way.
- Mikro, Logo, Parasut, Shopify, WordPress
- Separate scope analysis if no ready module exists
- Data direction and mapping responsibility
Share product data by permission
Two Delbig accounts can build a product source relationship.
- Product, image, price and catalog permissions
- Automatic or approval-based sync
- Dealer, sub-store or second Delbig account
Example Flow
How should an integration project be planned?
- Scenario is selected. API-out, ready integration, API-in or Delbig-to-Delbig product sharing are separated.
- Source and receiver are defined. Decide which company, account or system is the source and which side receives data.
- Sharing permissions are written. Product, price, image, catalog, stock, customer, quote or order fields are clarified.
- Automatic or manual model is selected. Decide whether changes flow automatically or wait for approval on the receiving side.
- Ready connection status is checked. If a ready module exists it can be activated; otherwise custom scope is reviewed separately.
- Live use is monitored. Sync records, error handling and change policies are followed with operations.
Positioning
This module is ready API infrastructure; every custom connector is not included in one fixed fee
Delbig API / Integration provides API access, authorization logic, integration structure and Delbig-to-Delbig product sharing infrastructure. But every third-party system has a different data model, security flow and API standard.
For this reason, Mikro, Logo, Parasut, Shopify, WordPress or custom software connections may be published as ready modules or scoped as separate projects. The page should make this distinction clearly.
API / Integration module
Covers API access, permission model, data sharing, Delbig-to-Delbig product source and integration infrastructure.
Ready or custom connectors
Mikro, Logo, Parasut, Shopify, WordPress or custom software links are handled as ready modules or separate project scope.
Related Pages
Which modules should be reviewed with API / Integration?
Integration is added when there is a need for external API access, Delbig-to-Delbig product sharing or ready connector usage.
Store Operations
If product, price, stock and catalog data will feed sub-stores or different sales channels from one source, review together.
Dealer Portal
Dealer catalog, price visibility and B2B order workflows can be planned together with permission-based product integration.
Manufacturer Operations
If the manufacturer will share product catalog data with dealers or sub-accounts, source-company roles are clarified with this package.
Ready integrations
Mikro, Logo, Parasut, Shopify and WordPress connections can be selected separately when they are published as ready modules.
Module Fee
API / Integration module price
4,750 TL / yr + VAT is shown as the current annual fee. This module is added on top of the selected main package when needed.
This is the usage fee for the API / Integration module. Custom third-party connectors, special field mapping and development work can be scoped separately.
Help
Frequently asked questions
Who is this module suitable for?
Companies that want to expose Delbig data through API, use ready integration modules or share product/price/catalog data between Delbig accounts with permissions.
Is it included in the main package?
No. External system connection is not required for every customer, so API / Integration is a separate add-on module.
Does this module provide access to Delbig API documentation?
Yes. With the right permission scope, Delbig quote, order, customer, product and similar data can be exposed through API.
Are Mikro, Logo, Parasut or Shopify connectors included in this fee?
If a ready integration module is published, it can be activated separately. If no ready module exists, the third-party connector is scoped as a custom project and is not automatically included in this module fee.
Can two Delbig companies connect product data with each other?
Yes. The source company can open permitted products, images, prices or catalog fields to another Delbig account. The receiving side can use automatic or approval-based integration.
Is custom integration development included in this price?
No. The visible annual module fee is the add-on usage fee. Custom development, special data mapping or third-party adaptation may be priced separately after scope analysis.
Manage Delbig data with API access, ready integrations and permission-based product sharing
If you need API access, ready connectors or product integration between Delbig accounts, select API / Integration on the pricing page and then clarify the scope together.