CIAMA
English
API & integrations
Your catalogue already lives in an ERP or PIM. Your orders need to reach your business applications. The CIAMA API lets you build these exchanges and use your data in the operations that matter to your teams.
Your source and destination systems: API exchanges are scoped by software, version and business data. Connections depend on scope or require an integration assessment. No official partnership is claimed.
View connections and availabilityData your teams can use
Feed CIAMA
Products, brands and categories from your ERP or PIM
Customers, commercial terms, orders and deliveries
Suppliers, purchase orders and receipts
CIAMAAPIThe cockpit for your operations
Catalogue · orders · purchases · inventoryUse the data
Centralised orders, lines and shipments to retrieve
Exposed data and metrics for business reporting
Accessible references and operations for your own workflows
01 / Use cases
Start with a specific operation. Data already held in your tools can feed CIAMA; data centralised in CIAMA can be retrieved by your applications.
Your ERP or PIM → CIAMA
Send products, brands, categories and tags from your system of record. Source identifiers keep the link to records in your existing tools.
Feed the CIAMA catalogue from existing data to avoid entering the information covered by the integration again.
Explore this use case ↗CIAMA → your applications
Retrieve orders centralised in CIAMA, their lines and shipments to use them in your ERP or internal applications.
Your team can build the flow into its own processing workflows using operations already brought together in CIAMA.
Explore this use case ↗Your systems → CIAMA
Feed suppliers, purchase orders and receipts from your systems. Find these operations in the context of your product references.
Purchasing and logistics share a view of what is ordered, received and still expected, without rebuilding this tracking manually in CIAMA.
Explore this use case ↗Your B2B activity → CIAMA
Send the business customers, pricing terms, offers, orders and deliveries needed for your B2B scope.
Review business sales alongside your other operations while keeping references from your commercial system.
Explore this use case ↗
Your source inventory → CIAMA
Feed reference inventory from your systems into availability and replenishment workflows. Useful exchanges are scoped with your logistics data sources.
Your teams can connect the quantities supplied with product references and cockpit operations. Current API stock writes cover the default warehouse; exchanges for external warehouses are scoped separately.
Explore this use case ↗CIAMA → your reporting tools
Use exposed resources, including order line data and available metrics for brands or categories.
Build a view suited to your organisation with accessible data, known costs and explicit limitations, according to the resources in your instance.
Explore this use case ↗02 / A practical example
Your ERP can remain the starting point for the catalogue. CIAMA brings operations together around products; your application then retrieves the data useful for its own processing.
The integration feeds the product into CIAMA with its source identifier and the agreed information.
The product provides a shared reference for examining integrated orders and purchases when their identities are matched.
Your team uses centralised orders and their lines to feed its ERP or internal workflow.
The project defines reference mappings, exchanged data and outcome checks. Your ERP and applications keep the responsibilities you assign to them.
See how to connect your ERP and sales channels ↗03 / Your first connection
A catalogue to feed, orders to retrieve or receipts to track: identify the work to support and the teams involved.
Agree which tool is the source of record, which identifiers connect products and how often information needs to move.
Your team, your partner or DAWAP builds the agreed exchanges using the access and documentation for your instance.
Check received data, errors to handle and the result in the business workflow before extending the exchanges.
04 / Your integration options
Your developers or service provider can build the connection using the API documentation. Define the exchanges and operating responsibilities together.
We can scope the flows and build a custom integration. The connection work is specified separately from CIAMA modules and licensing.
A dedicated instance managed by DAWAP or installation on your servers: integration takes account of your network, source systems and processing volumes.
05 / For your technical team
Methods, formats, access and responses are described in the documentation for your instance. Your team can use it to prepare and verify the data exchanges.
Request the documentation matching your version of CIAMA and your proposed scope.
Request API documentation ↗Yes. The project defines each tool’s role in product data, orders, purchases and inventory. The API can feed supported resources into CIAMA and retrieve exposed data for your applications. Your systems of record remain explicit.
Yes. Your developers or service provider can build the exchanges with suitable documentation and access. DAWAP can also deliver a custom connection if you prefer.
Choose a specific operation useful to your teams: feeding the catalogue, retrieving orders or tracking purchases and receipts. We review the data and expected outcome to define an initial scope, then useful extensions.
Frequency depends on the flow, connected systems, volumes and your instance. It is agreed during scoping. Updating a resource and refreshing metrics are separate operations.
Warehouse operations in CIAMA and available API resources have distinct scopes. The current foundation supports warehouse reads and writes to default reference inventory. Warehouse creation, external warehouse writes and extended 3PL reads are extensions to scope; each flow is checked for your project.
The API provides resources for supported exchanges. Connecting your ERP or application requires mappings, rules and checks. Existing integrations and any development needed are identified during scoping.
Tell us about your tools and the operation you want to improve. We will review the useful data, connection options and a practical starting scope.
Discuss my integration ↗